← all publishers

drafael

@drafael source repo

Report this profile Claim this profile

• 21 skills
• 0 followers
• 14 hours ago last updated

1. ▌
   Skill Hunter · drafael bundle

   Use when the user wants to find NEW external skills for a project, build a skill stack from external registries, or compare external options against project needs. Do not use for questions about how to use already-installed/local skills.
   0
   installs
2. ▌
   Diagram Design · drafael bundle

   Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, deployment, dependency graph, UML class, story map, or database schema diagrams as standalone HTML/SVG/PNG. Redraw .drawio/.drawio.png/.drawio.svg or Mermaid .mmd sources at a chosen size/detail; onboard brand tokens from a website; add semantic patterns, callouts, accessible motion, or sketchy/hand-drawn styling.
   0
   installs
3. ▌
   Arena · drafael bundle

   Produce and compare at least two independent attempts at the same concrete artifact, then return one coherent synthesis with its verification result. Manual invocation only for direct use; an explicitly invoked workflow whose instructions permit arena delegation may run a bounded phase while retaining final judgment. Do not use to split a larger task into different work slices.
   0
   installs
4. ▌
   Teach · drafael bundle

   Teach repository-backed code and engineering work through a progressive, evidence-grounded conversation. Manual invocation only; use when the user explicitly invokes teach to understand a change, subsystem, architecture, runtime behavior, or evidenced rationale. Read-only; do not modify files.
   0
   installs
5. ▌
   Wrong · drafael bundle

   Reset after the user rejects the assistant's current answer, plan, implementation, or problem-solving direction. Use for "your approach is wrong", "start over", "try a different approach", or when the attempted solution has demonstrably failed. Use clarify for incorrect system behavior and brainstorm when the user wants multiple new designs or alternatives.
   0
   installs
6. ▌
   Unslop · drafael bundle

   Edit or review prose to remove formulaic AI-writing patterns while preserving facts, meaning, and the author's existing voice. Use for small style-only edits, articles, reports, messages, release notes, and other prose, or as the final pass after substantial technical writing. When technical-writing is available, use it first for substantial technical documentation and design artifacts. Do not use for code-only tasks or text that must remain verbatim.
   0
   installs
7. ▌
   Clarify · drafael bundle

   Investigate expected-versus-actual behavior, suspected defects, and historical design rationale. Use when someone asks why observed behavior differs from expectations, whether behavior is wrong, or why a design decision exists. Use explain-code for neutral questions about what code does or how it works, and wrong when the user rejects the assistant's current approach.
   0
   installs
8. ▌
   Reflect · drafael bundle

   Review the current session for durable, evidence-backed improvements to existing local skills. Manual invocation only; use when the user explicitly asks to reflect or run a session retrospective. Never edit skills or perform external actions without individual approval.
   0
   installs
9. ▌
   Architect · drafael bundle

   Produce an implementation-ready, caller-first structural design for a sufficiently understood engineering problem. Manual invocation only; use when the user explicitly asks to architect a change or define its types, signatures, data structures, and module boundaries. Use brainstorm for unresolved future behavior and explain-code for a neutral current-code walkthrough.
   0
   installs
10. ▌
    Autopilot · drafael bundle

    Compile a bounded coding objective, independent queue, or ordered stack into an immutable charter and run it through the restart-resumable Autopilot CLI. Manual invocation only; use when the user explicitly invokes Autopilot for unattended or resumable autonomous implementation with checkable completion conditions and explicit Git or delivery authority.
    0
    installs
11. ▌
    Brainstorm · drafael bundle

    Explore unresolved future behavior, architecture, ownership, features, or substantive alternatives through collaborative dialogue before implementation. Use when the user explicitly asks to brainstorm, explore options, or think through a future change, or when another active skill identifies consequential decisions that still need exploration. Use explain-code for neutral current-code walkthroughs, architect when explicitly invoked for implementation-ready structural design, and technical-writing when available to structure an agreed design.
    0
    installs
12. ▌
    Java Coder · drafael bundle

    Mandatory for every task in a Java codebase, including planning, implementation, debugging, refactoring, review, testing, Maven or Gradle build and dependency changes, performance or security analysis, and Java-related documentation. Detect Java projects from pom.xml, Gradle files, gradlew, or .java sources. Load before inspecting or changing the repository even when the user does not explicitly mention Java. Covers Java 21+, Spring Boot, Swing/EDT, code style, testing, security, and desktop UI.
    0
    installs
13. ▌
    Code Review · drafael bundle

    Find actionable defects and risks through a focused, evidence-based review of correctness, regressions, security, performance, architecture, and testing. Use for requests to review, audit, critique, or identify improvements. Use blast-radius, when explicitly invoked and available, for cross-boundary consequence tracing and executable safety proof of a concrete change. Use explain-code when the user only wants to understand current behavior or architecture.
    0
    installs
14. ▌
    Debug Error · drafael bundle

    Systematically debug and fix errors using structured investigation. Use when the user asks to "debug", "fix an error", "troubleshoot", "investigate a bug", or shares an error message or stack trace.
    0
    installs
15. ▌
    Write Tests · drafael bundle

    Write unit, integration, component, and end-to-end tests for code. Use when the user asks to "write tests", "add tests", "add test coverage", or "create test cases" for functions, services, components, CLIs, or user flows.
    0
    installs
16. ▌
    Blast Radius · drafael bundle

    Analyze a concrete code change for credible breakage beyond the obvious diff and seek executable proof for the assumptions that make it safe. Manual invocation only; use for an explicitly requested blast-radius analysis of a local diff, commit range, branch comparison, or local patch.
    0
    installs
17. ▌
    Explain Code · drafael bundle

    Explain current code behavior, structure, runtime flow, data flow, and component ownership. Use for ordinary walkthroughs, line-by-line explanations, subsystem mental models, and questions about what code does or how it works. Use teach, when explicitly invoked and available, for progressive learning; technical-writing, when available, for substantial standalone documentation; clarify for expectation mismatches or historical intent; code-review for finding problems; refactor-code for structural changes; brainstorm for unresolved future design; and architect, when explicitly invoked and available, for implementation-ready structural design.
    0
    installs
18. ▌
    Refactor Code · drafael bundle

    Change existing code through narrow, behavior-preserving, test-backed simplification without speculative architecture or scope growth. Use for requests to refactor, clean up, restructure, or simplify code. Use explain-code instead when the user only wants an explanation of the current structure.
    0
    installs
19. ▌
    Test Coverage · drafael bundle

    Analyze and improve test coverage. Use when reviewing coverage gaps, writing missing tests, setting up coverage tooling, or improving branch/line/statement coverage for any language or framework.
    0
    installs
20. ▌
    Typescript Coder · drafael bundle

    Mandatory for every task in a TypeScript or mixed TypeScript codebase, including planning, implementation, debugging, refactoring, review, testing, dependency and build changes, CI, security analysis, and TypeScript-related documentation. Detect projects from tsconfig files, .ts/.tsx sources, TypeScript dependencies, or TypeScript framework configuration. Load before inspecting or changing such repositories. Covers Node.js, Bun, existing Deno projects, backend, frontend, CLI/TUI, Electron, Electrobun, Tauri, AWS CDK, and modern tooling.
    0
    installs
21. ▌
    Technical Writing · drafael bundle

    Write, revise, or review substantial technical documentation and design artifacts for a defined reader and task. Use for READMEs, guides, tutorials, how-to documentation, reference material, runbooks, RFCs, ADRs, technical specifications, and implementation plans. Use a design workflow first when future behavior or architecture needs exploration. Use unslop, when available, for small style-only edits. Do not use for code-only work, routine messages, release notes, PR descriptions, commit messages, or verbatim text.
    0
    installs