EnigmaWU

WHEN/WHERE/WHO: [Scheduling: Architects or agents wanting to translate passive technical reference books or engineering standards into executable agent skills.] HOW: [Structural: Use this COMPLEX SKILL to extract actionable workflows, choose the correct tier,…

WHEN/WHERE/WHO: AI Agents or users generating a new skill for the repository. HOW: Use this SKILL to automatically scaffold a new skill directory, format the `SKILL.md` with the correct tier template (SIMPLE/COMPLICATED/COMPLEX), apply the standardized YAML…

WHEN/WHERE/WHO: Software architects, engineers, or agents who need to critique or review software architecture diagrams (images, PDF pages, diagram-as-code, or pasted descriptions) against the C4 model rules from Simon Brown's "The C4 Model" book. HOW:…

WHEN/WHERE/WHO: Use when a user asks to review an existing repository, project, platform, pipeline, or architecture as a data engineering project; trigger phrases include "review data engineering", "review-data-engineering", "review-data-enginneering", "data…

WHEN/WHERE/WHO: Product designers, UX researchers, architects, and AI agents should use this skill when asked to design an autonomous AI interface, agentic product UX, AI copilots that plan or act, human-in-the-loop controls, AI workflow checkpoints, or…

WHEN/WHERE/WHO: [Scheduling: Use when: defining a test strategy or planning tests for a feature. Applies to: test planning, feature review, acceptance criteria] HOW: [Structural: Helps with: balancing test coverage across business/technology and…

WHEN/WHERE/WHO: [Scheduling: Software architects or lead developers designing a new feature or greenfield system.] HOW: [Structural: Use this SKILL to systematically execute the 7-step ADD 3.0 methodology to map drivers to design patterns.] WHY: [Scheduling:…

WHEN/WHERE/WHO: [Scheduling: Analysts, researchers, product teams, and agents creating or reviewing charts, dashboards, reports, or infographics.] HOW: [Structural: Use this SKILL to select the right chart for the analytical task, apply perception-safe visual…

Save the current conversation as a reusable skill. Use when: a long conversation finally solved a hard problem, complex debugging session completed, multi-step workflow discovered, or non-obvious solution found after trial and error. Make sure to use this…

Create a cross-agent skill extraction system with 3-layer auto-discovery (.prompt.md, SKILL.md, .instructions.md). Use when: building a /save-as-skill slash command, setting up skill files for Copilot/Cline/Continue/Claude Code, integrating Anthropic…

Use when: driving a user story through SpecCoding from issue or feature input to detail design, acceptance criteria, testing, implementation, review, commit, CI, closure, or abort. Helps with: user-story-centered SpecCoding using Px-SpecFlow lifecycle…

Use when: writing new tests from scratch, designing verification for a new feature or module, applying CaTDD, starting a new test file with comment-alive design. Helps with: creating structured test files using CaTDD (Comment-alive Test-Driven Development)…