Menu
SkillsMP has collected 59 skills from EnigmaWU/MyCodeAgentSkills. Open a skill to review its source and details.
Showing 40 of 59 collected skills.
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…
WHEN/WHERE/WHO: [Scheduling: Business analysts, testers, or agents exploring user journeys or data workflows.] HOW: [Structural: Use this SKILL to work backward from the business Outcome, to tangible Outputs, to the Process, down to Scenarios and exact…
WHEN/WHERE/WHO: [Scheduling: SDETs, developers, or agents writing or refactoring automated acceptance tests.] HOW: [Structural: Use this SKILL to structure test code around Actors, Tasks, Interactions, Abilities, and Questions rather than Page Objects.] WHY:…
WHEN/WHERE/WHO: [Scheduling: Product owners, BAs, testers, developers, and agents aligning requirements with delivery.] HOW: [Structural: Use this SKILL to derive scope from goals, specify collaboratively with examples, refine for clarity, automate…
WHEN/WHERE/WHO: [Scheduling: Database designers, business analysts, or agents analyzing forms, reports, or data-heavy requirements.] HOW: [Structural: Use this SKILL to extract domain nouns from text and map them into a strict Data Dictionary (Element Name,…
WHEN/WHERE/WHO: [Scheduling: 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. Applies to: new test files for UnitTesting, SysTesting, and…
WHEN/WHERE/WHO: [Scheduling: Architects, domain experts, product owners, or agents analyzing a new business domain or complex workflow.] HOW: [Structural: Use this SKILL to facilitate a Big Picture Event Storming session, discovering Domain Events…
WHEN/WHERE/WHO: [Scheduling: System architects, analysts, or agents defining the scope of a new project.] HOW: [Structural: Use this SKILL to extract all upstream and downstream systems from text and render them as a Mermaid.js graph.] WHY: [Scheduling:…
WHEN/WHERE/WHO: [Scheduling: Use when: automating specifications, extracting domain glossaries, generating PlantUML/Graphviz architecture diagrams, or creating BDD reconciliation tests. Applies to: codebase architecture, glossary generators, API schemas, and…
WHEN/WHERE/WHO: [Scheduling: Use when: defining the structural views of a system, documenting system architecture, or aligning stakeholder expectations. Applies to: software architecture descriptions, system design documents, and RFCs] HOW: [Structural: Helps…
WHEN/WHERE/WHO: [Scheduling: Developers, database designers, or agents designing the object-oriented domain layer of a system.] HOW: [Structural: Use this SKILL to strictly apply Vaughn Vernon's 4 Rules of Aggregate Design to shape entities and value…
WHEN/WHERE/WHO: [Scheduling: Use when: the user asks to create or update documentation. Applies to: markdown documents, READMEs, guides, and runbooks] HOW: [Structural: Helps with: producing docs that always include 5W1H context and a copy-exec Usage Example]…
WHEN/WHERE/WHO: [Scheduling: Architects, system designers, or agents resolving an architectural tradeoff. Applies to design proposals and RFCs.] HOW: [Structural: Use this SKILL to write structured 12-field Architectural Decision Records (ADRs) and…
WHEN/WHERE/WHO: [Scheduling: Business analysts, systems engineers, or agents compiling requirements into a final specification.] HOW: [Structural: Use this SKILL to map scattered user stories, constraints, and UI notes into the formal IEEE-style SRS…
WHEN/WHERE/WHO: [Scheduling: Business analysts, agents, or developers reviewing complex user stories or PRDs.] HOW: [Structural: Use this SKILL to parse text requirements into Mermaid.js visual models (state/flow diagrams) to identify missing logic.] WHY:…
WHEN/WHERE/WHO: [Scheduling: Business analysts or agents reviewing user stories or PRDs that contain embedded business logic.] HOW: [Structural: Use this SKILL to extract policies, laws, and calculations from text and categorize them into a strict Business…
WHEN/WHERE/WHO: [Scheduling: Business analysts, Product Owners, or agents leading a Backlog Refinement or "Three Amigos" session.] HOW: [Structural: Use this SKILL to decompose a User Story into Business Rules (Blue), Concrete Examples (Green), and Open…
WHEN/WHERE/WHO: [Scheduling: Use when a user or Product Owner wants to break down an epic, feature, or new product idea into a structured User Story Map.] HOW: [Structural: Use this SKILL to explicitly execute the state-machine phases of Context Gathering,…
WHEN/WHERE/WHO: [Scheduling: Developers, product owners, QA engineers, or agents keeping BDD-style user stories up to date.] HOW: [Structural: Use this SKILL to proactively detect when a conversation introduces a new edge case or change, and update the…
WHEN/WHERE/WHO: [Scheduling: Use when an AI Agent needs to bootstrap a C/C++ project with robust testing and security guardrails.] HOW: [Structural: Use this SKILL to inject a standardized CMakeLists.txt that auto-discovers Google Tests and supports Clang/GCC…
WHEN/WHERE/WHO: [Scheduling: Developers or agents who have just finished a task and want a structured commit message.] HOW: [Structural: Use this SKILL to auto-trigger a commit prompt and generate a structured WHAT/HOW/WHY git commit.] WHY: [Scheduling:…
WHEN/WHERE/WHO: [Scheduling: Use when: the user asks to create a demo test case, example test, UserGuide demo, UserStories demo, manual demo, setup-backed test case, or explicitly invokes test-case-with-demo. Applies to: documentation-oriented P4 demo/example…
WHEN/WHERE/WHO: [Scheduling: Use when: the user creates a new test case, plans to write a test, or asks to generate a readme for an existing test. Applies to: any test creation workflow or existing test files like ] HOW: [Structural: Helps with: planning and…
WHEN/WHERE/WHO: [Scheduling: Developers or agents implementing any new feature, bugfix, or refactoring.] HOW: [Structural: Use this SKILL to strictly enforce the Red-Green-Refactor cycle. No production code without a failing test first.] WHY: [Scheduling:…
WHEN/WHERE/WHO: [Scheduling: Developers or agents refactoring tests to CaTDD. Applies to existing test files lacking US/AC/TC structure.] HOW: [Structural: Use this SKILL to extract User Stories, Acceptance Criteria, and Test Cases from legacy code into the…
WHEN/WHERE/WHO: [Scheduling: Developers or agents analyzing a freshly solved, non-trivial problem to update the user's resume.] HOW: [Structural: Use this SKILL to write a structured entry (WHAT problem, HOW approached, WHAT gained) in both EN and ZH…
WHEN/WHERE/WHO: [Scheduling: QA engineers, agents, or business analysts reviewing drafted requirements before development.] HOW: [Structural: Use this SKILL to hunt for ambiguous words, identify edge cases, and translate the text into strict BDD Acceptance…
WHEN/WHERE/WHO: [Scheduling: Product owners or agents analyzing project kickoff documents or vision statements.] HOW: [Structural: Use this SKILL to map subjective Business Problems to quantifiable Business Objectives, and derive the Product Concept.] WHY:…
WHEN/WHERE/WHO: [Scheduling: Analysts or agents reviewing flat product backlogs or lengthy PRDs.] HOW: [Structural: Use this SKILL to group unstructured requirements into a hierarchical Feature Tree (L1, L2, L3) rendered as a mindmap.] WHY: [Scheduling: Flat…
WHEN/WHERE/WHO: [Scheduling: System analysts or architects analyzing raw product requirements before design begins.] HOW: [Structural: Use this SKILL to extract and formalize unstructured requirements into the four types of architectural drivers.] WHY:…
WHEN/WHERE/WHO: [Scheduling: Software architects, domain experts, or agents splitting a monolith or designing a microservices architecture.] HOW: [Structural: Use this SKILL to partition the system into Subdomains and map the integration contracts using…
WHEN/WHERE/WHO: [Scheduling: Domain experts, developers, or agents analyzing raw business requirements.] HOW: [Structural: Use this SKILL to extract a strict Ubiquitous Language glossary for a specific Bounded Context. Reject synonyms, define exact…
WHEN/WHERE/WHO: [Scheduling: Developers, product owners, or agents formalizing requirements into backlog items.] HOW: [Structural: Use this SKILL to write User Stories backed strictly by BDD "Given/When/Then" executable specifications.] WHY: [Scheduling:…