Loading...
Loading...
Found 62 Skills
Code generation with Codex delegation. Understands task, finds patterns, delegates to Codex, validates output. Use when: implementing a feature, writing code, building functionality.
Orchestrate a multi-phase implementation workflow for this repository with artifact files under .ai/<project-name>/<letter>/ and fresh codex exec child runs per phase. Use when the user wants one prompt to drive context gathering, planning, plan assessment, implementation, build verification, and review iterations while keeping the main session context clean.
This skill should be used when the user works on any .ex or .exs file, mentions Elixir/Phoenix/Ecto/OTP, the project has a mix.exs, or asks "which skill should I use", "new to Elixir", "help with Elixir". Routes to the correct thinking skill BEFORE exploring code. Triggers on "implement", "add", "fix", "refactor" in Elixir projects.
This skill synchronizes plugin skills (plugins/synapse-a2a/skills/) with the current implementation, README.md, and guides folder. Use this skill when implementation changes have been made, new features added, or documentation updated, to ensure plugin skills stay up-to-date. Triggered by /sync-plugin-skills command or when significant code changes are detected.
Implement the minimal code needed to make failing tests pass in the TDD green phase.
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Especialista em implementação de código no SynkOS. Use esta skill quando o usuário pedir para implementar uma story, desenvolver uma feature, corrigir um bug, escrever testes, refatorar código, ou fazer perguntas como "desenvolva a story X", "implemente o critério de aceite Y", "corrija esse erro", "escreva os testes para Z", "aplique as correções do review". Ative também para entregas técnicas autônomas (modo yolo), para geração de handoff ao finalizar milestones, e para atualização da lista de arquivos modificados em uma story. Não iniciar implementação sem critérios de aceite definidos.
Router over the workflow catalog. Ask which skill or flow fits your situation and get pointed at the right one. Use when unsure where to start.
Run the SPARC Architecture and Implementation phases — design module boundaries, write pseudocode, implement code, and run tests
Implement a piece of work based on a spec or set of tickets.
Use when implementing an approved written plan or confirmed coding outcome in an existing repository, including requests to build, add, change, or write code.
When the boundaries are clear, directly implement code, tests and necessary documentation, and complete the implementation and closure with minimal interruptions