all publishers

mopeyjellyfish

@mopeyjellyfish source repo

64 published skills

  1. ▌
    Run 2 · mopeyjellyfish bundle
    Optionally orchestrate remaining Flywheel stages. Use only when one coordinated pass is better than manual stage handoffs.
    1 repo stars
  2. ▌
    Tdd 2 · mopeyjellyfish bundle
    Enforce red-green-refactor for feature work, bug fixes, refactors, and behavior changes.
    1 repo stars
  3. ▌
    Docs 2 · mopeyjellyfish bundle
    Write or refresh Diataxis project docs. Use when setup, APIs, CLI flows, config, workflows, or behavior changed.
    1 repo stars
  4. ▌
    Plan 2 · mopeyjellyfish bundle
    Create read-only implementation plans. Use for requirements, bug reports, feature ideas, or rough tasks before execution.
    1 repo stars
  5. ▌
    Spin 2 · mopeyjellyfish bundle
    Capture durable lessons in docs/solutions. Use after completed work, verified fixes, or repeated repo-specific patterns.
    1 repo stars
  6. ▌
    Work 2 · mopeyjellyfish bundle
    Execute ready implementation work. Use for plans, specs, todos, or clear requests that need tracked changes and validation.
    1 repo stars
  7. ▌
    Debug 2 · mopeyjellyfish bundle
    Investigate hard bugs, regressions, stack traces, or broken behavior with evidence, a repro loop, causal proof, and a fix path.
    1 repo stars
  8. ▌
    Setup 2 · mopeyjellyfish bundle
    Diagnose and bootstrap repo-local setup. Use for onboarding, workflow readiness, host posture, or missing tool checks.
    1 repo stars
  9. ▌
    Shape 2 · mopeyjellyfish bundle
    Shape work before implementation. Use to choose ideation, brainstorming, planning, or plan-deepening before work.
    1 repo stars
  10. ▌
    Start 2 · mopeyjellyfish bundle
    Route project work through Flywheel. Use to pick the earliest useful stage from shape, work, review, spin, or commit.
    1 repo stars
  11. ▌
    Commit 2 · mopeyjellyfish bundle
    Finish a branch cleanly. Use to verify readiness, make logical commits, push, and create or refresh a PR with evidence.
    1 repo stars
  12. ▌
    Deepen 2 · mopeyjellyfish bundle
    Grill and strengthen an existing plan. Use to align source docs, decisions, vertical slices, tests, and rollout before work.
    1 repo stars
  13. ▌
    Ideate 2 · mopeyjellyfish bundle
    Generate and filter grounded next bets. Use when the work is not chosen and the user wants ranked ideas before brainstorming.
    1 repo stars
  14. ▌
    Polish 2 · mopeyjellyfish bundle
    Run an interactive browser polish loop. Use to tighten browser-visible work with live feedback before review or commit.
    1 repo stars
  15. ▌
    Review 2 · mopeyjellyfish bundle
    Run structured code review. Use before PRs or merges to find bugs, regressions, missing tests, and readiness gaps.
    1 repo stars
  16. ▌
    Verify 2 · mopeyjellyfish bundle
    Verify completion claims with fresh evidence. Use before claiming tests, lint, builds, fixes, or requirements are done.
    1 repo stars
  17. ▌
    Logging 2 · mopeyjellyfish bundle
    Design or review structured logging. Use when runtime behavior needs useful events, stable fields, or correlation IDs.
    1 repo stars
  18. ▌
    Rollout 2 · mopeyjellyfish bundle
    Plan release posture for runtime-risky changes. Use for validation, sequencing, rollout, rollback, and blast radius.
    1 repo stars
  19. ▌
    Decision 2 · mopeyjellyfish bundle
    Grill and capture durable decisions. Use for ADRs, terminology conflicts, tradeoffs, or spec decision review.
    1 repo stars
  20. ▌
    Incident 2 · mopeyjellyfish bundle
    Handle runtime incidents from live evidence. Use to bound blast radius and choose mitigation, rollback, or patch.
    1 repo stars
  21. ▌
    Optimize 2 · mopeyjellyfish bundle
    Run measured optimization loops. Use for latency, throughput, resource, cost, build, or query improvements that need proof.
    1 repo stars
  22. ▌
    Research 2 · mopeyjellyfish bundle
    Research a topic with repo and current-source evidence. Use when findings should sharpen shaping, review, or planning.
    1 repo stars
  23. ▌
    Simplify 2 · mopeyjellyfish bundle
    Reduce accidental complexity in recent code. Use when wrappers, abstractions, or orchestration no longer earn their keep.
    1 repo stars
  24. ▌
    Worktree 2 · mopeyjellyfish bundle
    Manage isolated git worktrees. Use for branch work, isolated review targets, parallel checkouts, or cleanup.
    1 repo stars
  25. ▌
    Brainstorm 2 · mopeyjellyfish bundle
    Explore requirements and approaches. Use for a fuzzy idea, open scope, or one direction that needs sharper behavior before planning.
    1 repo stars
  26. ▌
    Browser Test 2 · mopeyjellyfish bundle
    Run browser acceptance checks with playwright-cli. Use when browser-visible behavior needs fresh proof before review or commit.
    1 repo stars
  27. ▌
    Observability 2 · mopeyjellyfish bundle
    Design or review runtime observability. Use for logs, metrics, traces, dashboards, validation, and supportability.
    1 repo stars
  28. ▌
    Commit Message 2 · mopeyjellyfish bundle
    Draft Conventional Commit messages. Use when choosing a commit header, body, footer, or breaking-change marker.
    1 repo stars
  29. ▌
    Document Review 2 · mopeyjellyfish bundle
    Review requirements or plan docs. Use to surface severity, confidence, and a ranked fix queue before planning or work.
    1 repo stars
  30. ▌
    Maintainability 2 · mopeyjellyfish bundle
    Assess future edit cost. Use when wrappers, helpers, naming, cohesion, or ownership may make changes harder.
    1 repo stars
  31. ▌
    Pattern Recognition 2 · mopeyjellyfish bundle
    Assess pattern fit from repo truth. Use when deciding whether DTOs, repositories, ports, builders, DDD, or similar patterns fit.
    1 repo stars
  32. ▌
    Architecture Strategy 2 · mopeyjellyfish bundle
    Assess repo-grounded architecture choices and improvements. Use for boundaries, service splits, dependency direction, or distributed posture.
    1 repo stars
  33. ▌
    Run · mopeyjellyfish bundle
    Optionally orchestrate remaining Flywheel stages. Use only when one coordinated pass is better than manual stage handoffs.
    1 repo stars
  34. ▌
    Tdd · mopeyjellyfish bundle
    Enforce red-green-refactor for feature work, bug fixes, refactors, and behavior changes.
    1 repo stars
  35. ▌
    Docs · mopeyjellyfish bundle
    Write or refresh Diataxis project docs. Use when setup, APIs, CLI flows, config, workflows, or behavior changed.
    1 repo stars
  36. ▌
    Plan · mopeyjellyfish bundle
    Create read-only implementation plans. Use for requirements, bug reports, feature ideas, or rough tasks before execution.
    1 repo stars
  37. ▌
    Spin · mopeyjellyfish bundle
    Capture durable lessons in docs/solutions. Use after completed work, verified fixes, or repeated repo-specific patterns.
    1 repo stars
  38. ▌
    Work · mopeyjellyfish bundle
    Execute ready implementation work. Use for plans, specs, todos, or clear requests that need tracked changes and validation.
    1 repo stars
  39. ▌
    Debug · mopeyjellyfish bundle
    Investigate hard bugs, regressions, stack traces, or broken behavior with evidence, a repro loop, causal proof, and a fix path.
    1 repo stars
  40. ▌
    Setup · mopeyjellyfish bundle
    Diagnose and bootstrap repo-local setup. Use for onboarding, workflow readiness, host posture, or missing tool checks.
    1 repo stars
  41. ▌
    Shape · mopeyjellyfish bundle
    Shape work before implementation. Use to choose ideation, brainstorming, planning, or plan-deepening before work.
    1 repo stars
  42. ▌
    Start · mopeyjellyfish bundle
    Route project work through Flywheel. Use to pick the earliest useful stage from shape, work, review, spin, or commit.
    1 repo stars
  43. ▌
    Commit · mopeyjellyfish bundle
    Finish a branch cleanly. Use to verify readiness, make logical commits, push, and create or refresh a PR with evidence.
    1 repo stars
  44. ▌
    Deepen · mopeyjellyfish bundle
    Grill and strengthen an existing plan. Use to align source docs, decisions, vertical slices, tests, and rollout before work.
    1 repo stars
  45. ▌
    Ideate · mopeyjellyfish bundle
    Generate and filter grounded next bets. Use when the work is not chosen and the user wants ranked ideas before brainstorming.
    1 repo stars
  46. ▌
    Polish · mopeyjellyfish bundle
    Run an interactive browser polish loop. Use to tighten browser-visible work with live feedback before review or commit.
    1 repo stars
  47. ▌
    Review · mopeyjellyfish bundle
    Run structured code review. Use before PRs or merges to find bugs, regressions, missing tests, and readiness gaps.
    1 repo stars
  48. ▌
    Verify · mopeyjellyfish bundle
    Verify completion claims with fresh evidence. Use before claiming tests, lint, builds, fixes, or requirements are done.
    1 repo stars
  49. ▌
    Logging · mopeyjellyfish bundle
    Design or review structured logging. Use when runtime behavior needs useful events, stable fields, or correlation IDs.
    1 repo stars
  50. ▌
    Rollout · mopeyjellyfish bundle
    Plan release posture for runtime-risky changes. Use for validation, sequencing, rollout, rollback, and blast radius.
    1 repo stars
  51. ▌
    Decision · mopeyjellyfish bundle
    Grill and capture durable decisions. Use for ADRs, terminology conflicts, tradeoffs, or spec decision review.
    1 repo stars
  52. ▌
    Incident · mopeyjellyfish bundle
    Handle runtime incidents from live evidence. Use to bound blast radius and choose mitigation, rollback, or patch.
    1 repo stars
  53. ▌
    Optimize · mopeyjellyfish bundle
    Run measured optimization loops. Use for latency, throughput, resource, cost, build, or query improvements that need proof.
    1 repo stars
  54. ▌
    Research · mopeyjellyfish bundle
    Research a topic with repo and current-source evidence. Use when findings should sharpen shaping, review, or planning.
    1 repo stars
  55. ▌
    Simplify · mopeyjellyfish bundle
    Reduce accidental complexity in recent code. Use when wrappers, abstractions, or orchestration no longer earn their keep.
    1 repo stars
  56. ▌
    Worktree · mopeyjellyfish bundle
    Manage isolated git worktrees. Use for branch work, isolated review targets, parallel checkouts, or cleanup.
    1 repo stars
  57. ▌
    Brainstorm · mopeyjellyfish bundle
    Explore requirements and approaches. Use for a fuzzy idea, open scope, or one direction that needs sharper behavior before planning.
    1 repo stars
  58. ▌
    Browser Test · mopeyjellyfish bundle
    Run browser acceptance checks with playwright-cli. Use when browser-visible behavior needs fresh proof before review or commit.
    1 repo stars
  59. ▌
    Observability · mopeyjellyfish bundle
    Design or review runtime observability. Use for logs, metrics, traces, dashboards, validation, and supportability.
    1 repo stars
  60. ▌
    Commit Message · mopeyjellyfish bundle
    Draft Conventional Commit messages. Use when choosing a commit header, body, footer, or breaking-change marker.
    1 repo stars
  61. ▌
    Document Review · mopeyjellyfish bundle
    Review requirements or plan docs. Use to surface severity, confidence, and a ranked fix queue before planning or work.
    1 repo stars
  62. ▌
    Maintainability · mopeyjellyfish bundle
    Assess future edit cost. Use when wrappers, helpers, naming, cohesion, or ownership may make changes harder.
    1 repo stars
  63. ▌
    Pattern Recognition · mopeyjellyfish bundle
    Assess pattern fit from repo truth. Use when deciding whether DTOs, repositories, ports, builders, DDD, or similar patterns fit.
    1 repo stars
  64. ▌
    Architecture Strategy · mopeyjellyfish bundle
    Assess repo-grounded architecture choices and improvements. Use for boundaries, service splits, dependency direction, or distributed posture.
    1 repo stars