latent-space-engineering
Shapes agent behavior via instruction framing and style transfer. Use when composing dispatch prompts or writing skill instructions for parallel review agents.
What this skill does
# 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 |
Related in methodology
six-thinking-hats
IncludedApply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).
xp-practices
IncludedApply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.