all publishers

limonequantistico

@limonequantistico source repo

32 published skills

  1. ▌
    Env · limonequantistico
    Audit environment variables, secrets hygiene, and production readiness. Use only when the user explicitly asks for an env or secrets review or runs /env.
    0 repo stars
  2. ▌
    A11Y · limonequantistico
    Run a WCAG-focused accessibility pass on the current UI, driving the real running app when it can be reached. Use only when the user explicitly asks for an accessibility/a11y review or runs /a11y.
    0 repo stars
  3. ▌
    Deps · limonequantistico
    Update dependencies to latest stable versions and align tech-stack.md. Use only when the user explicitly asks to bump or update dependencies or runs /deps.
    0 repo stars
  4. ▌
    Help · limonequantistico
    Show the docsygen workflow guide — the full command reference and recommended order. Use only when the user explicitly asks for help or runs /help.
    0 repo stars
  5. ▌
    Init · limonequantistico
    Scaffold the baseline .docs/ structure and CLAUDE.md that other docsygen skills depend on, and bring a project set up under an older docsygen up to current conventions (idempotent). Use only when the user explicitly asks to initialize or update docsygen in this project, or runs /init.
    0 repo stars
  6. ▌
    Logs · limonequantistico
    Establish or audit application logging — what gets recorded, at what level, with what context — shaped to the project's architecture and existing stack. Use only when the user explicitly asks about logging or runs /logs.
    0 repo stars
  7. ▌
    Push · limonequantistico
    Commit and push the current branch in one shot — generates the commit message, then stages, commits, and pushes. Never opens a PR and never merges (use /merge for that). Use only when the user explicitly asks to commit and push, or runs /push.
    0 repo stars
  8. ▌
    Seed · limonequantistico
    Create the seed document from raw notes in .docs/idea.md, or integrate new notes into an existing seed. Use only when the user explicitly asks to create or update the seed or runs /seed.
    0 repo stars
  9. ▌
    Test · limonequantistico
    Define or improve automated testing strategy and critical-path coverage. Use only when the user explicitly asks about testing strategy or runs /test.
    0 repo stars
  10. ▌
    Tidy · limonequantistico
    Archive completed backlog items to the changelog (backlog cleanup only). Use only when the user explicitly asks to tidy the backlog or runs /tidy.
    0 repo stars
  11. ▌
    Clean · limonequantistico
    Audit the codebase for modularity, structure, and separation of concerns, then refactor on approval. Use only when the user explicitly asks to clean up structure or runs /clean.
    0 repo stars
  12. ▌
    Debug · limonequantistico
    Diagnose a specific reported bug from runtime evidence rather than guesswork — competing hypotheses, instrumentation, a reproduction, a root-cause fix, then cleanup. Use only when the user explicitly asks to debug a broken behaviour, or runs /debug.
    0 repo stars
  13. ▌
    Drift · limonequantistico
    Find where the docs and the codebase have diverged — direction, stack, design, components — and propose a fix for each, in whichever direction is right. Use only when the user explicitly asks to check doc drift or reconcile docs with code, or runs /drift.
    0 repo stars
  14. ▌
    Merge · limonequantistico
    One-shot ship, branch-aware — generate a commit message, then commit and either open+merge a PR against main (on a feature branch) or push straight to main (when already on main). Use only when the user explicitly asks to ship/merge the current work or runs /merge.
    0 repo stars
  15. ▌
    Setup · limonequantistico
    Wire the design system into code and build base components. Use only when the user explicitly asks to set up styles or components or runs /setup.
    0 repo stars
  16. ▌
    Stack · limonequantistico
    Define the project's tech stack in .docs/tech-stack.md. Use only when the user explicitly asks to define the stack or runs /stack.
    0 repo stars
  17. ▌
    Commit · limonequantistico
    Produce a copyable commit message for the latest changes (does not run git commit). Use only when the user explicitly asks for a commit message or runs /commit.
    0 repo stars
  18. ▌
    Resume · limonequantistico
    Give a fresh situational assessment after time away — what changed, what is next, what is off. Use only when the user explicitly asks to resume or runs /resume.
    0 repo stars
  19. ▌
    Review · limonequantistico
    Read-only review of uncommitted changes for bugs before commit, OR triage of another agent's review of your work. Use only when the user explicitly asks to review changes or runs /review.
    0 repo stars
  20. ▌
    To Prd · limonequantistico
    Turn the current conversation context into a Product Requirement Document (PRD) and save it under .docs/prds/. Use when user wants to create a PRD from the current context.
    0 repo stars
  21. ▌
    Onboard · limonequantistico
    Produce or refresh onboarding docs and README so another dev can run and contribute. Use only when the user explicitly asks to refresh onboarding docs or runs /onboard.
    0 repo stars
  22. ▌
    Version · limonequantistico
    Cut a new app version — summarize changes since last release and write to versions.json. Use only when the user explicitly asks to cut a version or runs /version.
    0 repo stars
  23. ▌
    Scaffold · limonequantistico
    Validate or create the project structure based on the tech stack. Use only when the user explicitly asks to scaffold or runs /scaffold.
    0 repo stars
  24. ▌
    Prototype · limonequantistico
    Generate a paste-ready prompt for external design tools (Claude Design, Stitch, Figma AI, V0) to create screens and prototypes. Use only when the user explicitly asks to prototype or runs /prototype.
    0 repo stars
  25. ▌
    To Issues · limonequantistico
    Break a plan, spec, or PRD into independently-grabbable items using tracer-bullet vertical slices, then write them to .docs/backlog.md or to GitHub Issues. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into tasks.
    0 repo stars
  26. ▌
    UX Review · limonequantistico
    Get the agent's eyes on the real running product, then run a UI/UX quality check — hierarchy, flow, consistency, cognitive load. Sets up and records a reusable way to actually see the app. Use only when the user explicitly asks for a UX review or runs /ux-review.
    0 repo stars
  27. ▌
    Deep Audit · limonequantistico
    Deep whole-codebase audit for latent bugs, security holes, broken failure paths, and architectural risk — report first, fix only on approval. Use only when the user explicitly asks for a deep audit of the codebase, or runs /deep-audit.
    0 repo stars
  28. ▌
    Performance · limonequantistico
    Review performance and observability — bottlenecks, baselines, metrics, tracing. Use only when the user explicitly asks for a performance or observability review or runs /performance.
    0 repo stars
  29. ▌
    Seed Review · limonequantistico
    Stress-test the seed document (scope, riskiest assumption, gaps) with a Proceed/Revise/Rethink verdict. Use only when the user explicitly asks to review the seed or runs /seed-review.
    0 repo stars
  30. ▌
    Herdr Review · limonequantistico
    Automated second-opinion review — spawn a reviewer agent in a herdr pane, capture its review of the uncommitted changes, triage the findings, and apply the ones that hold up. Use only when the user explicitly asks for an automated or herdr-based second-opinion review, or runs /herdr-review. Requires herdr (HERDR_ENV=1).
    0 repo stars
  31. ▌
    Design System · limonequantistico
    Define the project's design system (visual tokens and decisions) in .docs/design-system.md through a guided interview — proposing options and letting the user choose before anything is written. Use only when the user explicitly asks to define the design system or runs /design-system.
    0 repo stars
  32. ▌
    Domain Modeling · limonequantistico bundle
    Build and sharpen a project's domain model — ubiquitous language (CONTEXT.md) and Architecture Decision Records (ADRs). Use only when the user explicitly asks to pin down domain terminology or record an architectural decision, runs /domain-modeling, or when another skill (e.g. /grill-with-docs) composes it.
    0 repo stars