all publishers

yknothing

@yknothing source repo

126 published skills · page 2 of 2

  1. ▌
    Pc Market Analysis · yknothing bundle
    Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a new product or expansion idea before feasibility, user research, or requirements are finalized.
    1 repo stars
  2. ▌
    Pc Systematic Debugging · yknothing bundle
    Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code changes, especially when brownfield seams, recent releases, or historical defect matches make guesswork unsafe.
    1 repo stars
  3. ▌
    Pc Tech Debt Management · yknothing bundle
    Use when repeated findings from reviews, incidents, retrospectives, or delivery friction need to be turned into a prioritized technical-debt registry and remediation plan, especially when brownfield seams, release-boundary gaps, or operational workarounds are accruing real engineering cost.
    1 repo stars
  4. ▌
    Pc Receiving Code Review · yknothing bundle
    Use when review feedback has arrived and the author must verify, sequence, and respond to comments without blind agreement, especially when suggestions may conflict with brownfield constraints, contracts, or existing architecture decisions.
    1 repo stars
  5. ▌
    Pc Feasibility Study · yknothing bundle
    Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.
    1 repo stars
  6. ▌
    Pc Monitoring Observability · yknothing bundle
    Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
    1 repo stars
  7. ▌
    Pc Requirements Engineering · yknothing bundle
    Use when the work is still at the “what should we build” stage and approved discovery inputs or entry-stack outputs must become prioritized requirements and scope boundaries before specification, architecture, planning, or coding. Not for acceptance criteria, spec review, or implementation.
    1 repo stars
  8. ▌
    Pc Internationalization · yknothing bundle
    Use when user-facing text, locale-sensitive formatting, or multi-language behavior need explicit rules so copy, layout, and data presentation stay correct across locales.
    1 repo stars
  9. ▌
    Pc Bug History Retrieval · yknothing bundle
    Use when a current bug, incident, regression, or recurring symptom may match a known internal defect and the agent needs canonical evidence from issue trackers, incident systems, error monitoring, or git history before choosing a fix or next debugging step.
    1 repo stars
  10. ▌
    Pc Verification Before Completion · yknothing bundle
    Use when about to claim a phase, fix, task, build, or release is complete, fixed, passing, or ready for handoff and fresh evidence must be checked before making the claim or creating a commit, PR, or deployment decision.
    1 repo stars
  11. ▌
    Pc Implementation Integrity Audit · yknothing bundle
    Use after code changes when the reviewer must aggressively audit low-level defects, deceptive implementations, improper mocks, fake evidence, and test shortcuts before a delivery claim is trusted.
    1 repo stars
  12. ▌
    Pc Implementation Alignment Review · yknothing bundle
    Use after implementation or repair work when the reviewer must judge intent realization, requirement coverage, scope consistency, and claim truth before code-review or delivery-completion can accept the work.
    1 repo stars
  13. ▌
    Problem Framing · yknothing
    Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly
    1 repo stars
  14. ▌
    CI CD · yknothing
    Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
    1 repo stars
  15. ▌
    Tdd · yknothing
    Use when a reviewed task is ready for implementation and the team must drive the work by writing failing tests first, especially when contract behavior, brownfield regressions, unsupported flows, or coexistence safety must be proven before code changes.
    1 repo stars
  16. ▌
    Spec Writing · yknothing
    Use when reviewed requirements need a shared product or technical specification that fixes scope, non-goals, interfaces, rollout concerns, and open questions before architecture or implementation. Skip for routine agile story refinement.
    1 repo stars
  17. ▌
    Code Review · yknothing
    Use when a concrete code change is ready for review and the reviewer must evaluate correctness, security, maintainability, test adequacy, contract alignment, and brownfield safety before merge, especially when unsupported flows, backward compatibility, or release-boundary constraints must be enforced.
    1 repo stars
  18. ▌
    Data Modeling · yknothing
    Use when the system structure is known and the team must turn domain concepts and architectural boundaries into durable storage schemas, ownership rules, and migration-safe data flow decisions before implementation.
    1 repo stars
  19. ▌
    Task Breakdown · yknothing
    Use when reviewed architecture or API contracts must be decomposed into implementation-ready work items, especially when sequencing, reversible brownfield increments, dependency mapping, and vertical slices must be explicit before coding begins.
    1 repo stars
  20. ▌
    Testing Strategy · yknothing
    Use when a reviewed implementation slice or feature needs a deliberate test plan across unit, integration, contract, and end-to-end layers, especially when brownfield regressions, unsupported flows, coexistence boundaries, or API contracts require explicit coverage beyond the default happy path.
    1 repo stars
  21. ▌
    Domain Modeling · yknothing
    Use when reviewed requirements still carry ambiguous business nouns, overlapping concepts, or possible bounded contexts, and the team needs a shared domain model before spec writing, API design, or data modeling.
    1 repo stars
  22. ▌
    API Design · yknothing
    Use when architecture boundaries are already defined and the team must specify stable API contracts between components or for external consumers, especially when backward compatibility, brownfield coexistence, authorization rules, and error semantics must be made explicit before implementation.
    1 repo stars
  23. ▌
    Security Design · yknothing
    Use when the architecture is defined and the team must turn trust boundaries, sensitive data paths, and attacker assumptions into concrete control design before implementation and audit.
    1 repo stars
  24. ▌
    User Research · yknothing
    Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written
    1 repo stars
  25. ▌
    System Design · yknothing
    Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
    1 repo stars
  26. ▌
    Requirements Engineering · yknothing
    Use when the work is still at the “what should we build” stage rather than design or implementation. Apply before spec-writing, architecture, API design, planning, or coding when interviews, personas, stakeholder notes, or discovery artifacts must be turned into prioritized functional requirements, non-functional requirements, scope boundaries, traceable sources, and explicit “the system shall” statements; not for acceptance criteria, PRD drafting from an approved requirements doc, spec review, or implementation.
    1 repo stars