all publishers

nono911

@nono911 source repo

21 published skills

  1. ▌
    Plan · nono911 bundle
    Use when a software direction is defined enough to map multi-step, cross-cutting, risky, or long-running work into a proportionate, verifiable execution plan; use brainstorm first when the direction is still open.
    1 repo stars
  2. ▌
    Test · nono911 bundle
    Use when software behavior needs automated unit, integration, contract, end-to-end, edge-case, or regression tests, or coverage assessment; use acceptance-verify for manual runtime QA of a running user journey.
    1 repo stars
  3. ▌
    Debug · nono911 bundle
    Use when behavior is wrong, failing, flaky, slow, inconsistent, or unexplained and the root cause must be isolated from runtime evidence; use bugfix-loop only when its full isolated fix-and-review workflow is explicitly requested.
    1 repo stars
  4. ▌
    Review · nono911 bundle
    Use for a general objective code, diff, PR, or fix review without edits; use architecture-review or security-review when either is the primary assessment objective.
    1 repo stars
  5. ▌
    Handoff · nono911 bundle
    Use only when explicitly asked to prepare a continuation packet, session transfer, or ownership handoff so another agent or human can resume unfinished work without replaying the conversation.
    1 repo stars
  6. ▌
    Estimate · nono911 bundle
    Use when software work needs an evidence-based range for effort, duration, sequencing, risk, staffing, or confidence before commitment.
    1 repo stars
  7. ▌
    Refactor · nono911 bundle
    Use when internal code structure, naming, duplication, coupling, complexity, or module boundaries should improve without changing externally observable behavior.
    1 repo stars
  8. ▌
    Implement · nono911 bundle
    Use for general software implementation from a requirement, spec, issue, or plan; use fix-findings instead when validated findings are the primary work queue.
    1 repo stars
  9. ▌
    Migration · nono911 bundle
    Use when data, schema, API, dependency, platform, infrastructure, or runtime state must move between versions or systems while preserving service and recoverability.
    1 repo stars
  10. ▌
    API Design · nono911 bundle
    Use when creating or changing an HTTP, RPC, event, webhook, library, or internal service contract and consumers need a stable, evolvable interface.
    1 repo stars
  11. ▌
    Brainstorm · nono911 bundle
    Use when a product, feature, technical approach, workflow, or problem space needs proportionate, distinct options explored before a direction is chosen; use plan after the direction and constraints are sufficiently settled.
    1 repo stars
  12. ▌
    Bugfix Loop · nono911 bundle
    Use when user requests an isolated bugfix with regression proof, commits, independent review, and fixes; use debug and implement for fixes.
    1 repo stars
  13. ▌
    Write Guide · nono911 bundle
    Use when the primary task is to create or update a user guide, onboarding guide, setup guide, admin or operator manual, tutorial, or help-center documentation from current product behavior, including UI screenshots when useful; verify material runnable steps and mark anything not observed instead of inventing it. Do not activate solely for a one-off explanation, work item, API contract, or agent handoff.
    1 repo stars
  14. ▌
    Fix Findings · nono911 bundle
    Use when validated review, audit, QA, or security findings are the primary work queue and must be corrected and verified; use implement for a general requirement or feature.
    1 repo stars
  15. ▌
    Delivery Loop · nono911 bundle
    Use when the user requests isolated feature delivery with commits, bounded independent review, and fixes; use implement for feature work.
    1 repo stars
  16. ▌
    Database Design · nono911 bundle
    Use when designing or changing persistent data models, schemas, constraints, indexes, transactions, tenancy, retention, or query patterns.
    1 repo stars
  17. ▌
    Security Review · nono911 bundle
    Use when security is the primary assessment objective for code, configuration, architecture, identities, data handling, or a change set; use review for a general defect review.
    1 repo stars
  18. ▌
    Acceptance Verify · nono911 bundle
    Use when an agent must execute QA, manual UI testing, UAT, browser testing, or acceptance verification of a running user journey and report runtime evidence without fixing code; use test when the primary goal is to author automated tests.
    1 repo stars
  19. ▌
    Release Readiness · nono911 bundle
    Use when a change, branch, build, migration, or release candidate must be assessed before merge, deployment, rollout, or handoff.
    1 repo stars
  20. ▌
    Architecture Review · nono911 bundle
    Use when architecture is the primary review objective for boundaries, coupling, ownership, scalability, resilience, maintainability, or long-term change cost; use review for a general defect review.
    1 repo stars
  21. ▌
    Communicate Clearly · nono911 bundle
    Use when the primary task is to explain, summarize, compare options, report status, request a decision, rewrite human-facing text, or draft or update work items such as epics, stories, issues, tickets, tasks, and subtasks; do not activate solely to restyle implementation, review, testing, or debugging work.
    1 repo stars