Menu
Skills in this repository
SkillsMP has collected 59 skills from EnigmaWU/MyCodeAgentSkills. Open a skill to review its source and details.
EnigmaWU/MyCodeAgentSkillsShowing 19 of 59 collected skills.
WHEN/WHERE/WHO: [Scheduling: Use when designing the context-gathering tools (Abilities) for an autonomous agent, especially when mixing fast APIs and slow UI interactions.] HOW: [Structural: Use this SKILL to separate "Fast Thinking" (API queries) from "Slow…
WHEN/WHERE/WHO: [Scheduling: Agents or architects designing systems capable of handling complex, multi-step tasks that require forward thinking.] HOW: [Structural: Use this SKILL to implement ReAct (Reason + Act) or Plan-and-Solve workflows, decoupling task…
WHEN/WHERE/WHO: [Scheduling: Use when designing the exit criteria and validation logic for an autonomous AI agent's execution loop.] HOW: [Structural: Use this SKILL to translate classic BDD Gherkin scenarios into Verifiable Reward Functions that act as hard…
WHEN/WHERE/WHO: [Scheduling: Use when an AI Agent or Architect is designing the core reasoning and execution loop for a multi-agent or autonomous system.] HOW: [Structural: Use this SKILL to define the system strictly in terms of Actors (Agents), Abilities…
WHEN/WHERE/WHO: [Scheduling: Use when: designing a multi-agent system, creating routing logic, building self-correcting prompt chains, or adding tool-use and planning capabilities. Applies to: orchestration scripts, agent system designs, and prompt chain…
WHEN/WHERE/WHO: [Scheduling: Agents or users declaring durable expertise, preferences, or personal defaults.] HOW: [Structural: Use this SKILL to activate the personal profile and update it when new durable information is provided.] WHY: [Scheduling: Prevents…
WHEN/WHERE/WHO: [Scheduling: Reviewers, architects, or agents analyzing a proposed or existing architecture.] HOW: [Structural: Use this SKILL to systematically evaluate the design against targeted Quality Attribute questionnaires (e.g., Availability,…
WHEN/WHERE/WHO: [Scheduling: Use when: designing a system architecture, conducting structural design reviews, or mapping quality goals to design decisions. Applies to: architecture design documents, RFCs, and system design specifications] HOW: [Structural:…
WHEN/WHERE/WHO: [Scheduling: Use when: a task is completed, a goal is met, or the user asks to review recent work for blog ideas. Applies to: post-task reflection and developer branding] HOW: [Structural: Helps with: extracting insights, mistakes, new…
WHEN/WHERE/WHO: [Scheduling: Agents or developers designing memory layers for autonomous agents that must retain context across sessions.] HOW: [Structural: Use this SKILL to configure short-term working memory, semantic vector stores, and episodic event logs…
WHEN/WHERE/WHO: [Scheduling: Agents or architects granting LLMs access to terminal commands, file systems, or external APIs.] HOW: [Structural: Use this SKILL to enforce boundary protections, user-approval loops, and containerized execution for dangerous…
WHEN/WHERE/WHO: [Scheduling: Use when: reverse-engineering brownfield systems, mapping legacy code structures, establishing bubble context boundaries, or applying strangler migration patterns. Applies to: legacy libraries, brownfield codebases, boundary…
WHEN/WHERE/WHO: [Scheduling: Developers or DevOps engineers deploying autonomous agents to production who need to monitor costs and behavior.] HOW: [Structural: Use this SKILL to inject trace IDs, token tracking, and structured logging into all agent tool…
WHEN/WHERE/WHO: [Scheduling: Agents or architects designing self-correcting loops for LLM-based tasks where high-quality output is critical.] HOW: [Structural: Use this SKILL to set up an Evaluator-Generator loop, explicitly separating the generation logic…
WHEN/WHERE/WHO: [Scheduling: Agents or architects designing systems where distinct domain experts must collaborate to produce a final result.] HOW: [Structural: Use this SKILL to design a Supervisor or Coordinator-Specialist topology, defining clear message…
WHEN/WHERE/WHO: [Scheduling: Product owners or agents grooming a backlog of features or user stories.] HOW: [Structural: Use this SKILL to score items across Value, Cost, and Risk using an analytical matrix, yielding a strict rank order.] WHY: [Scheduling:…
WHEN/WHERE/WHO: [Scheduling: Use when: a vibe-coding or AI-assisted coding conversation changes requirements, design decisions, plans, task status, or implementation context. Applies to: GitHub Spec Kit-style specs, plans, tasks, constitutions, and repository…
WHEN/WHERE/WHO: [Scheduling: Use when the user says "save as skill", "capture this as a skill", or "turn this into a skill", or when a long solved conversation produced a reusable workflow that would be expensive to rediscover. Do not use for trivial…
WHEN/WHERE/WHO: [Scheduling: Use when an existing skill was applied, did not fully solve the problem, and the user says "improve this skill", "update the skill", "the skill needs fixing", "make this skill better", or "this skill didn't work". Do not use for…