← all publishers

mopeyjellyfish

@mopeyjellyfish source repo

Report this profile Claim this profile

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

1. ▌
   Run · mopeyjellyfish bundle

   Optionally orchestrate remaining Flywheel stages. Use only when one coordinated pass is better than manual stage handoffs.
   0
   installs
2. ▌
   Tdd · mopeyjellyfish bundle

   Enforce red-green-refactor for feature work, bug fixes, refactors, and behavior changes.
   0
   installs
3. ▌
   Docs · mopeyjellyfish bundle

   Write or refresh Diataxis project docs. Use when setup, APIs, CLI flows, config, workflows, or behavior changed.
   0
   installs
4. ▌
   Plan · mopeyjellyfish bundle

   Create read-only implementation plans. Use for requirements, bug reports, feature ideas, or rough tasks before execution.
   0
   installs
5. ▌
   Spin · mopeyjellyfish bundle

   Capture durable lessons in docs/solutions. Use after completed work, verified fixes, or repeated repo-specific patterns.
   0
   installs
6. ▌
   Work · mopeyjellyfish bundle

   Execute ready implementation work. Use for plans, specs, todos, or clear requests that need tracked changes and validation.
   0
   installs
7. ▌
   Debug · mopeyjellyfish bundle

   Investigate hard bugs, regressions, stack traces, or broken behavior with evidence, a repro loop, causal proof, and a fix path.
   0
   installs
8. ▌
   Setup · mopeyjellyfish bundle

   Diagnose and bootstrap repo-local setup. Use for onboarding, workflow readiness, host posture, or missing tool checks.
   0
   installs
9. ▌
   Shape · mopeyjellyfish bundle

   Shape work before implementation. Use to choose ideation, brainstorming, planning, or plan-deepening before work.
   0
   installs
10. ▌
    Start · mopeyjellyfish bundle

    Route project work through Flywheel. Use to pick the earliest useful stage from shape, work, review, spin, or commit.
    0
    installs
11. ▌
    Commit · mopeyjellyfish bundle

    Finish a branch cleanly. Use to verify readiness, make logical commits, push, and create or refresh a PR with evidence.
    0
    installs
12. ▌
    Deepen · mopeyjellyfish bundle

    Grill and strengthen an existing plan. Use to align source docs, decisions, vertical slices, tests, and rollout before work.
    0
    installs
13. ▌
    Ideate · mopeyjellyfish bundle

    Generate and filter grounded next bets. Use when the work is not chosen and the user wants ranked ideas before brainstorming.
    0
    installs
14. ▌
    Polish · mopeyjellyfish bundle

    Run an interactive browser polish loop. Use to tighten browser-visible work with live feedback before review or commit.
    0
    installs
15. ▌
    Review · mopeyjellyfish bundle

    Run structured code review. Use before PRs or merges to find bugs, regressions, missing tests, and readiness gaps.
    0
    installs
16. ▌
    Verify · mopeyjellyfish bundle

    Verify completion claims with fresh evidence. Use before claiming tests, lint, builds, fixes, or requirements are done.
    0
    installs
17. ▌
    Logging · mopeyjellyfish bundle

    Design or review structured logging. Use when runtime behavior needs useful events, stable fields, or correlation IDs.
    0
    installs
18. ▌
    Rollout · mopeyjellyfish bundle

    Plan release posture for runtime-risky changes. Use for validation, sequencing, rollout, rollback, and blast radius.
    0
    installs
19. ▌
    Decision · mopeyjellyfish bundle

    Grill and capture durable decisions. Use for ADRs, terminology conflicts, tradeoffs, or spec decision review.
    0
    installs
20. ▌
    Incident · mopeyjellyfish bundle

    Handle runtime incidents from live evidence. Use to bound blast radius and choose mitigation, rollback, or patch.
    0
    installs
21. ▌
    Optimize · mopeyjellyfish bundle

    Run measured optimization loops. Use for latency, throughput, resource, cost, build, or query improvements that need proof.
    0
    installs
22. ▌
    Research · mopeyjellyfish bundle

    Research a topic with repo and current-source evidence. Use when findings should sharpen shaping, review, or planning.
    0
    installs
23. ▌
    Simplify · mopeyjellyfish bundle

    Reduce accidental complexity in recent code. Use when wrappers, abstractions, or orchestration no longer earn their keep.
    0
    installs
24. ▌
    Worktree · mopeyjellyfish bundle

    Manage isolated git worktrees. Use for branch work, isolated review targets, parallel checkouts, or cleanup.
    0
    installs
25. ▌
    Brainstorm · mopeyjellyfish bundle

    Explore requirements and approaches. Use for a fuzzy idea, open scope, or one direction that needs sharper behavior before planning.
    0
    installs
26. ▌
    Browser Test · mopeyjellyfish bundle

    Run browser acceptance checks with playwright-cli. Use when browser-visible behavior needs fresh proof before review or commit.
    0
    installs
27. ▌
    Observability · mopeyjellyfish bundle

    Design or review runtime observability. Use for logs, metrics, traces, dashboards, validation, and supportability.
    0
    installs
28. ▌
    Commit Message · mopeyjellyfish bundle

    Draft Conventional Commit messages. Use when choosing a commit header, body, footer, or breaking-change marker.
    0
    installs
29. ▌
    Document Review · mopeyjellyfish bundle

    Review requirements or plan docs. Use to surface severity, confidence, and a ranked fix queue before planning or work.
    0
    installs
30. ▌
    Maintainability · mopeyjellyfish bundle

    Assess future edit cost. Use when wrappers, helpers, naming, cohesion, or ownership may make changes harder.
    0
    installs
31. ▌
    Pattern Recognition · mopeyjellyfish bundle

    Assess pattern fit from repo truth. Use when deciding whether DTOs, repositories, ports, builders, DDD, or similar patterns fit.
    0
    installs
32. ▌
    Architecture Strategy · mopeyjellyfish bundle

    Assess repo-grounded architecture choices and improvements. Use for boundaries, service splits, dependency direction, or distributed posture.
    0
    installs