skills are the right tool for one bounded workflow. parallel subagents are the right tool when the same workflow must run across several independent units at once. the parent dispatches, aggregates, and keeps shared writes serial.
i recently reorganized how my repos load cursor rules, skills, and reference docs. the goal was token efficiency: less upfront context, lower cost, less waiting, and cleaner focus. the agent still fetches what it needs, but the baseline stays small.
this follow-up post gives practical, generic templates you can adapt for rules, skills, and commands, plus side-by-side examples that show why tighter structure improves ai execution quality.
this kickoff post explains why ai-authored rule, skill, and command scaffolds are often clearer for ai execution, and how to keep humans in control with constraints, reviews, and acceptance checks.