← ClaudeAtlas

writing-skillslisted

Use when creating a new skill, editing an existing skill, or verifying a skill works before deployment. Treats skill authoring as TDD for process documentation — baseline a pressure scenario, write the skill, confirm compliance, close loopholes. Triggers on "write/create/improve a skill", "add a SKILL.md", or changes to skill content.
StielChancellor/VibeGod-Tech-Team · ★ 0 · AI & Automation · score 62
Install: claude install-skill StielChancellor/VibeGod-Tech-Team
<!-- Adapted from superpowers (https://github.com/obra/superpowers), MIT (c) Jesse Vincent. --> # Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** Write test cases (pressure scenarios with subagents), watch them fail (baseline), write the skill, watch tests pass (agents comply), refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing. **REQUIRED BACKGROUND:** You MUST understand `test-driven-development` before using this skill — it defines the RED-GREEN-REFACTOR cycle this adapts to documentation. ## Fits in the pipeline Meta-skill — it builds the tools the pipeline runs on rather than sitting at one stage. Use it whenever you extend the VibeGod plugin (a new methodology skill, a domain skill, a role's playbook). Priority: **user > skills > default**; `_shared/vibegod-principles.md` apply. New skills must respect the same voice: crisp, imperative, no AI-slop hedging. ## What is a Skill? A reference guide for proven techniques, patterns, or tools that future Claude instances find and apply. **Skills ARE:** reusable techniques, patterns, tools, reference guides. **Skills are NOT:** narratives about how you solved a problem once. ## TDD Mapping for Skills | TDD Concept | Skill Creation | |-------------|----------------| | Test case | Pressure scenario with subagent | | Production code | Skill document (SKILL.md) |