Agent skill
latent-space-engineering
Shape agent behavior through instruction framing, emotional priming, and style transfer rather than information density alone.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/latent-space-engineering
SKILL.md
Latent Space Engineering
Shape agent behavior by framing instructions for optimal performance. Distinct from context engineering (packing the right information), this skill addresses HOW instructions are framed to put agents in productive mental states.
When To Use
- Composing agent dispatch prompts
- Writing skill instructions that guide behavior
- Dispatching 3+ parallel review agents
- Generating code or documentation that must match an existing style
When NOT To Use
- Packing factual context (use context-optimization)
- Simple single-shot tasks with no behavioral nuance
- Tasks where instruction tone is irrelevant
Core Techniques
1. Emotional Framing
Replace threat-based prompting with calm, confident instructions. Fear-based prompts cause rushing and corner-cutting.
Load module: modules/emotional-framing.md
2. Style Gene Transfer
Inject exemplar code or prose into context before requesting output. Agents reproduce stylistic attributes from pre-loaded samples.
Load module: modules/style-gene-transfer.md
3. Competitive Review
Frame multi-agent review dispatch with competitive incentives to increase rigor and thoroughness.
Load module: modules/competitive-review.md
Quick Reference
| Technique | When | Module |
|---|---|---|
| Emotional framing | Any agent prompt | emotional-framing |
| Style gene transfer | Code/doc generation | style-gene-transfer |
| Competitive review | 3+ parallel reviewers | competitive-review |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?