all publishers

seasonedcc

@seasonedcc source repo

190 published skills · page 1 of 2

  1. ▌
    Testing 9 · seasonedcc bundle
    Write and run unit tests with Vitest. Use when writing tests, adding test coverage, debugging test failures, or when the user mentions testing, vitest, unit tests, or test-driven development.
    4 repo stars
  2. ▌
    Skill Manager 4 · seasonedcc
    Create, manage, and debug Claude Code Agent Skills. Use when creating new skills, debugging skill activation issues, writing SKILL.md files, managing skill structure, or learning about Claude Code skills. Helps with personal skills, project skills, YAML frontmatter, descriptions, and troubleshooting.
    4 repo stars
  3. ▌
    Release 8 · seasonedcc
    Release a new version of the pagination-helpers npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.
    4 repo stars
  4. ▌
    Seasoned Skills 4 · seasonedcc
    Install, configure, upgrade, and repair the seasoned-skills workflow package — the source of this project's generated doctrine, skills, and runtime code. Use when installing or upgrading the workflow, changing seasoned-skills.config.ts, running or debugging the sync, reading a failed-sync report, or wiring a new machine. Also use when asked how this project's workflow is generated or where a generated file comes from.
    4 repo stars
  5. ▌
    Requests From Meetings 6 · seasonedcc bundle
    Parse meeting recordings into precise feature-request documents under ./requests-from-meetings. Use when the user invokes /requests-from-meetings, asks to parse a meeting or meeting backlog, asks what was requested or shown in a meeting, or mentions meeting recordings, transcripts, or feature requests from meetings.
    4 repo stars
  6. ▌
    Release 7 · seasonedcc
    Release a new version of the coerce-form-data npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.
    4 repo stars
  7. ▌
    Kysely 6 · seasonedcc
    Write Kysely queries and SQLite migrations following project conventions — CamelCasePlugin naming, builder over raw SQL, transactions, and regenerating app/db/types.d.ts. Use when writing a migration, creating a table or index, adding a column, writing a database query, using a transaction, or running db:migrate, db:rollback, or db:generate.
    4 repo stars
  8. ▌
    Testing 8 · seasonedcc
    Write and run Vitest unit tests against a real throwaway SQLite database and end-to-end specs that drive the real MCP server over stdio. Use when writing or fixing a test, running test:unit, test:e2e, or test:seed-coverage, practising TDD, mutation-proving an assertion, adding fixtures, editing the E2E seed or its fake gateway feed, writing a seed demonstration, or working on the tool coverage gate or the dev-seed coverage gate.
    4 repo stars
  9. ▌
    Env Vars 5 · seasonedcc
    Manage environment variables through the two-tier typed env pattern — a framework env and an app env, both built with make-typed-env and Zod. Use when adding or renaming an env var, editing app/framework/env.server.ts or app/env.server.ts, updating .env.example, or wiring configuration into framework, business, MCP, or ingest code.
    4 repo stars
  10. ▌
    Subagents 7 · seasonedcc
    Spawn subagents and dynamic workflows well — size each task to the context window (~33% of 1M target) and pick the right model tier. Use whenever delegating work to subagents, launching a Workflow, or deciding how to split a task across agents.
    4 repo stars
  11. ▌
    Worktrees 7 · seasonedcc
    Run parallel tasks in isolated git worktrees, each with its own env file and its own SQLite store. Use when creating or removing a worktree, running parallel lanes or agents, running gates or a server for a specific worktree, or when the user mentions worktree, parallel lanes, or isolated environments.
    4 repo stars
  12. ▌
    MCP Server 5 · seasonedcc
    Build and extend the MCP stdio server in app/mcp/ — the product's entire user surface — keeping the tool surface equal to the business surface. Use when adding or changing a tool, wiring a new domain into the server, editing app/mcp/*, working on the parity test or its exemptions, naming a tool, or shaping a tool's input schema at the JSON boundary.
    4 repo stars
  13. ▌
    Type Safety 5 · seasonedcc
    Write minimal, correct TypeScript — inference first, annotations only where removing them would lose safety, and no `any`. Use when adding types, declaring variables, writing a function signature, creating a type alias, deriving a type from a Zod schema, or reviewing code for redundant annotations and stray assertions.
    4 repo stars
  14. ▌
    Orchestration 9 · seasonedcc
    Run delegated work reliably — writing subagent charters, verifying subagent claims, keeping judgment at the orchestrator tier, ledger discipline, recovering from interruptions, and shipping and merging lane PRs. Use when spawning subagents or workflows, coordinating parallel lanes, resuming after a session limit or compaction, or rebasing and merging a lane's PR. The subagents skill covers task sizing and model choice; this skill covers everything after the spawn.
    4 repo stars
  15. ▌
    Skill Manager 3 · seasonedcc
    Create, manage, and debug Claude Code Agent Skills. Use when creating new skills, debugging skill activation issues, writing SKILL.md files, managing skill structure, or learning about Claude Code skills. Helps with personal skills, project skills, YAML frontmatter, descriptions, and troubleshooting.
    4 repo stars
  16. ▌
    Background Jobs 6 · seasonedcc
    Write background work against the in-process scheduler — makeJob and makeCronJob, registration in the jobs array, retries and dedupe, idempotency in an append-only store, fan-out, and the tests that prove each. Use when adding or changing a job, enqueuing work from business or ingest code, editing app/business/jobs.server.ts or app/framework/scheduler.server.ts, picking a retry or interval setting, or testing what a job runs and what it enqueues.
    4 repo stars
  17. ▌
    Business Folder 5 · seasonedcc
    Organize domain logic in app/business/ by domain cohesion and transport independence. Use when creating a file in app/business/, adding a function to one, naming a business module, deciding whether logic belongs in business or in a transport (app/mcp/, app/ingest/), or choosing what a business file may import.
    4 repo stars
  18. ▌
    Database Design 6 · seasonedcc
    Design SQLite tables and migrations under the project's zero-exception append-only, event-sourced doctrine. Use when creating tables, writing migrations, adding columns, modeling a state change, deriving current state, choosing between an identity and an event table, or writing the dev seed.
    4 repo stars
  19. ▌
    Framework Folder 5 · seasonedcc
    Enforce the separation between reusable framework code and product code in app/framework/. Use when adding a file or a helper to app/framework/, importing a framework module, wiring the database connection or the scheduler, or deciding where a new abstraction belongs.
    4 repo stars
  20. ▌
    Self Improvement 7 · seasonedcc
    Codify lessons from a completed task into repo improvements — skill updates, CLAUDE.md changes, or root-cause tooling fixes — delivered as PRs the user reviews and merges. Use when a task has met every other Definition of Done criterion, when a long effort concludes, or when the user asks to derive lessons from recent work.
    4 repo stars
  21. ▌
    Composable Functions 6 · seasonedcc bundle
    Build business functions with the composable-functions library — applySchema, context validation with capability flags, combinators, and Result handling. Use when writing or changing a function in app/business/, validating input or context, composing with pipe/sequence/all/collect/branch, throwing InputError or ContextError, or unwrapping results with fromSuccess.
    4 repo stars
  22. ▌
    Skill Manager 2 · seasonedcc
    Create, manage, and debug Claude Code Agent Skills. Use when creating new skills, debugging skill activation issues, writing SKILL.md files, managing skill structure, or learning about Claude Code skills. Helps with personal skills, project skills, YAML frontmatter, descriptions, and troubleshooting.
    4 repo stars
  23. ▌
    Docs Copywriting 2 · seasonedcc bundle
    Write human-facing prose for this repository in our voice — the README, every page under docs/, and any other copy a person reads. Use when writing or editing documentation, GitHub-facing text, or prose in release notes meant for human readers.
    4 repo stars
  24. ▌
    Quick 6 · seasonedcc
    Run a small fix or polish to an existing surface under a reduced quick-iteration Definition of Done — no subagents, no self-improvement pass. Use ONLY when the user explicitly invokes /quick; never select this mode on your own, never suggest it, and never let it self-trigger.
    4 repo stars
  25. ▌
    Release 6 · seasonedcc
    Cut a release — scope the span since the last release, deeply study every merged pull request in it, write release notes in which every sentence traces to a merged change, run the gates and audits, and treat the publish as the deliberate final act. Use when the user asks to release, cut a release, publish, ship a new version, ship what's on main, release to production, or write release notes.
    4 repo stars
  26. ▌
    Shaping 4 · seasonedcc
    Run framing and shaping sessions that end in a shaping document, and answer questions about the method from the verbatim books and posts in references/. Use when framing a raw idea, shaping a project, writing or revising a shaping document under shaping/, working feedback on one back in, breadboarding or drawing fat marker sketches, finding and defusing time bombs (Shape Up's rabbit holes), naming no-gos, or when reasoning about customer demand — jobs to be done, JTBD, the struggling moment, forces of progress, demand-side selling, why people switch. Also the corpus to consult on anything Shape Up covers beyond our process — pitches, appetite, betting tables, scopes, hill charts, scope hammering, deciding when to stop.
    4 repo stars
  27. ▌
    Testing 7 · seasonedcc
    Write, run, and debug tests across the project's unit and end-to-end suites. Covers test-driven development and mutation proofs, gate reconciliation, parallel-safe unit tests, E2E seeding and retry safety, coverage discipline, and diagnosing CI-only failures and flakes. Use when writing tests, fixing or diagnosing failing or flaky tests, running test suites, seeding E2E data, or when the user mentions testing, test-driven development, unit tests, E2E tests, or mutation proofs.
    4 repo stars
  28. ▌
    Reground 3 · seasonedcc
    Reground after a compaction — from this session's ledger and the real sources of truth, never from the compacted summary alone. Use ONLY when the user explicitly invokes /reground — the person types this command, never you.
    4 repo stars
  29. ▌
    Business Folder 3 · seasonedcc
    Organize business logic in app/business/ by domain cohesion and framework independence. Use when creating files in app/business/, adding functions to business files, naming business modules, deciding where to place business logic, or choosing what to import in business code.
    4 repo stars
  30. ▌
    Pr Review 4 · seasonedcc
    Review a GitHub pull request with full context — the description, every comment, review, and inline thread, then the diff — judging the big picture personally before multi-angle finding and adversarial verification. Use when asked to review a PR, analyze a pull request, assess a teammate's changes, or run the pre-merge adversarial review of a draft PR; use this instead of the native /review command.
    4 repo stars
  31. ▌
    Subagents 6 · seasonedcc
    Spawn subagents and dynamic workflows well — size each task to the context window (~33% of 1M target), pick the right model tier, and rule on agents that run past it. Use whenever delegating work to subagents, launching a Workflow, deciding how to split a task across agents, or handling a watchdog alert about a full context.
    4 repo stars
  32. ▌
    Worktrees 6 · seasonedcc
    Run parallel tasks in isolated git worktrees, each provisioned as a lane with its own databases, ports, env files, and services through the seasoned-skills binary. Use when creating or removing worktrees, provisioning or tearing down lanes, running parallel tasks or agents, starting a dev server for a specific lane, handing a lane to the user for manual testing, or when the user mentions worktree, parallel lanes, or isolated environments.
    4 repo stars
  33. ▌
    Env Vars 4 · seasonedcc
    Manage environment variables following the two-tier env pattern. Use when adding new env vars, modifying env schemas, working with app/framework/env.server.ts or app/env.server.ts, or updating CI env configuration.
    4 repo stars
  34. ▌
    Main Sync 5 · seasonedcc
    Sync a long-lived feature branch with its repo's advancing main — bring main's commits into the branch under the repository's sync strategy, judge the rule-set and capability deltas, and re-run the combined Definition of Done. Use when main gains commits under a goal or review-fixes feature branch, before syncing a feature branch with origin/main, or when deciding whether a feature landed on main must be mirrored on the branch.
    4 repo stars
  35. ▌
    Orchestration 8 · seasonedcc
    Run delegated work reliably — writing subagent charters, verifying subagent claims, keeping judgment at the orchestrator tier, ledger discipline, recovering from interruptions, and shipping/merging lane PRs. Use when spawning subagents or workflows, coordinating parallel lanes, resuming after a session limit or compaction, or rebasing and merging a lane's PR. The subagents skill covers task sizing and model choice; this skill covers everything after the spawn.
    4 repo stars
  36. ▌
    Demo Videos 5 · seasonedcc
    Produce the two narrated demo videos for a scope of work — a five-minute highlights cut and a full-length walkthrough — filmed from a screenplay against the seeded product. Use when the user invokes /demo-videos, asks for a demo video, demo videos, a screencast, a product walkthrough video, a narrated demo, video narration, a recording of what shipped, or a video to show stakeholders what a project delivered.
    4 repo stars
  37. ▌
    Post Review 4 · seasonedcc
    Post a completed code review on a teammate's GitHub PR as inline comments anchored to the diff, with the verdict and blocking rationale in the review summary. Use when posting review findings to GitHub, requesting changes or approving a PR, or after analyzing a PR (the pr-review skill covers the analysis) when the findings should land on the PR itself.
    4 repo stars
  38. ▌
    Review Fixes 4 · seasonedcc
    Turn a completed PR review's findings into an adjudicated fix scope and land the fixes on the reviewed PR's own branch — triage the certain defects, adjudicate everything else with the user one finding at a time, then orchestrate fix lanes merged into the feature branch. Use when fixing review findings on our own PR, addressing a pr-review analysis, or driving a reviewed PR toward a clean re-review.
    4 repo stars
  39. ▌
    Agent Browser 6 · seasonedcc bundle
    Automate browser interactions using the agent-browser CLI, and keep its sessions and processes from leaking. Use when navigating pages, clicking elements, filling forms, taking screenshots, extracting page data, running browser tests, verifying UI behavior, or cleaning up leftover browser processes. Use when the user mentions browser, agent-browser, test in browser, navigate, click, screenshot, interact with page, automate, leaked or runaway browsers, Chrome eating memory, or killing processes.
    4 repo stars
  40. ▌
    Authorization 5 · seasonedcc
    Implement authorization using context getters, context schemas, and composable functions. Use when working with authentication, permissions, user access control, protected routes, business logic authorization, or when user mentions auth, context, permissions, or access control.
    4 repo stars
  41. ▌
    Design System 5 · seasonedcc
    Follow the project's design system when building or changing UI. Use when creating pages, lists, forms, drawers, modals, badges, buttons, empty states, headings, or status indicators, when choosing icons, copy, button sizes, or breakpoints, when making a surface work on phones, tablets, or paper, or when the user mentions design system, UI patterns, visual consistency, typography, responsiveness, mobile, printing, or UX canon.
    4 repo stars
  42. ▌
    Nested Routes 4 · seasonedcc
    Create nested route sections with layouts, index redirects, and menu navigation in React Router v7. Use when adding new route groups, creating layouts with sidebar navigation, nesting routes under a parent path, or restructuring flat routes into nested ones.
    4 repo stars
  43. ▌
    Optimistic UI 5 · seasonedcc
    Build optimistic UI with React Router v7 using deterministic resource routes. Use when implementing toggles, optimistic updates, action-only routes, or when user mentions optimistic UI, toggle, or real-time feedback.
    4 repo stars
  44. ▌
    Seasoned Skills 3 · seasonedcc
    Install, configure, upgrade, and repair the seasoned-skills workflow package — the source of this project's generated doctrine, skills, and runtime code. Use when installing or upgrading the workflow, changing seasoned-skills.config.ts, running or debugging the sync, reading a failed-sync report, or wiring a new machine.
    4 repo stars
  45. ▌
    Self Improvement 6 · seasonedcc
    Codify lessons from a completed task on two channels at once — a draft pull request on the project's own content or tooling, plus a detailed anonymized issue on the seasoned-skills package — with every PR marked ready only by the user. Use when a task has met every other Definition of Done criterion, when a /goal goal is met but not yet marked complete, or when the user asks to derive lessons from recent work.
    4 repo stars
  46. ▌
    Skill Management 4 · seasonedcc
    Create, manage, and debug Claude Code Agent Skills. Use when creating new skills, debugging skill activation issues, writing SKILL.md files, managing skill structure, or learning about Claude Code skills. Helps with personal skills, project skills, YAML frontmatter, descriptions, and troubleshooting.
    4 repo stars
  47. ▌
    Business Folder 4 · seasonedcc
    Organize business logic in app/business/ by domain cohesion and framework independence. Use when creating files in app/business/, adding functions to business files, naming business modules, deciding where to place business logic, or choosing what to import in business code.
    4 repo stars
  48. ▌
    Framework Folder 4 · seasonedcc
    Enforce separation between framework and app code in the framework folder. Use when adding new files or logic to the framework folder, importing framework modules, or deciding where to place new abstractions.
    4 repo stars
  49. ▌
    Composable Functions 5 · seasonedcc bundle
    Work with composable-functions library for type-safe business logic. Use when working with applySchema, withContext, pipe, sequence, business functions, context validation, input validation, or when user mentions composable functions, schemas, or error handling patterns.
    4 repo stars
  50. ▌
    Prepare For Compaction 3 · seasonedcc
    Make this session's ledger current so its context can be compacted safely, then answer plainly that compacting is safe. Use ONLY when the user explicitly invokes /prepare-for-compaction — the person types this command, never you.
    4 repo stars
  51. ▌
    Requests From Meetings 5 · seasonedcc
    Parse meeting recordings into precise feature-request documents under ./requests-from-meetings. Use when the user invokes /requests-from-meetings, asks to parse a meeting or meeting backlog, asks what was requested or shown in a meeting, or mentions meeting recordings, transcripts, or feature requests from meetings.
    4 repo stars
  52. ▌
    Quick 2 · seasonedcc
    Run a small fix or polish to an existing surface under a reduced quick-iteration Definition of Done — no subagents, no mobile pass, no self-improvement pass. Use ONLY when the user explicitly invokes /quick; never select this mode on your own, and never suggest it.
    4 repo stars
  53. ▌
    Kysely 2 · seasonedcc
    Write Kysely queries and migrations following project conventions. Use when writing migrations, creating tables, adding columns, creating enums, writing database queries with Kysely, or using database transactions.
    4 repo stars
  54. ▌
    Kysely 3 · seasonedcc
    Write Kysely queries and migrations following project conventions. Use when writing migrations, creating tables, adding columns, creating enums, writing database queries with Kysely, or using database transactions.
    4 repo stars
  55. ▌
    Release 2 · seasonedcc
    Cut a production release — pick the next v<N> tag, deeply study everything merged since the last release, write curated release notes grouped by shaping project, solved meeting requests, and topic, stamp solved requests-from-meetings entries with Released badges, audit everything through a pre-release PR, then publish the GitHub Release that triggers the deploy. Use when the user invokes /release, asks to cut a release, release to production, ship what's on main, or write release notes.
    4 repo stars
  56. ▌
    Release 3 · seasonedcc
    Release new versions of the composable-controllers packages via Changesets. Analyze the diff, write the changeset, run checks, commit, ask the user to publish, and create per-package GitHub releases. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.
    4 repo stars
  57. ▌
    Testing 2 · seasonedcc bundle
    Write and run tests using Vitest (unit tests) and Playwright (E2E tests). Use when writing tests, fixing tests, running tests, implementing TDD, or when user mentions testing, test-driven development, Vitest, Playwright, unit tests, or E2E tests.
    4 repo stars
  58. ▌
    Testing 3 · seasonedcc
    Write and run tests for product-monolith using pytest (unit tests) and Playwright via pytest-playwright (E2E tests). Use when writing tests, fixing tests, running tests, implementing TDD, seeding E2E data, or when the user mentions testing, test-driven development, unit tests, E2E tests, Playwright, or mutation proofs.
    4 repo stars
  59. ▌
    Env Vars 2 · seasonedcc
    Manage environment variables following the two-tier env pattern. Use when adding new env vars, modifying env schemas, working with app/framework/env.server.ts or app/env.server.ts, or updating CI env configuration.
    4 repo stars
  60. ▌
    Quick 3 · seasonedcc
    Run a small fix or polish to an existing surface under a reduced quick-iteration Definition of Done — no subagents, no self-improvement pass. Use ONLY when the user explicitly invokes /quick; never select this mode on your own, never suggest it, and never let it self-trigger.
    4 repo stars
  61. ▌
    Quick 4 · seasonedcc
    Run a small fix or polish to an existing surface under a reduced quick-iteration Definition of Done — no subagents, no self-improvement pass. Use ONLY when the user explicitly invokes /quick; never select this mode on your own, never suggest it, and never let it self-trigger.
    4 repo stars
  62. ▌
    Kysely 4 · seasonedcc
    Write Kysely queries and migrations following project conventions. Use when writing migrations, creating tables, adding columns, creating enums, writing database queries with Kysely, or using database transactions.
    4 repo stars
  63. ▌
    Main Sync 2 · seasonedcc
    Sync a long-lived feature branch with its repo's advancing main — merge main in, judge the rule-set and capability deltas, and re-run the combined Definition of Done. Use when main gains commits under a goal or review-fixes feature branch, before merging origin/main into a feature branch, or when deciding whether a feature landed on main must be mirrored on the branch.
    4 repo stars
  64. ▌
    Pr Review 2 · seasonedcc
    Review a GitHub pull request with full context — the description, every comment, review, and inline thread, then the diff — judging the big picture personally before multi-angle finding and adversarial verification. Use when asked to review a PR, analyze a pull request, or assess a teammate's changes — including a PR by the founder, whose PRs the team takes over; use this instead of the native /review command.
    4 repo stars
  65. ▌
    Subagents 2 · seasonedcc
    Spawn subagents and dynamic workflows well — size each task to the context window (~33% of 1M target) and pick the right model tier. Use whenever delegating work to subagents, launching a Workflow, or deciding how to split a task across agents.
    4 repo stars
  66. ▌
    Subagents 3 · seasonedcc
    Spawn subagents and dynamic workflows well — size each task to the context window (~33% of 1M target), pick the right model tier, and rule on agents that run past it. Use whenever delegating work to subagents, launching a Workflow, deciding how to split a task across agents, or handling a watchdog alert about a full context.
    4 repo stars
  67. ▌
    Subagents 4 · seasonedcc
    Spawn subagents and dynamic workflows well — size each task to the context window (~33% of 1M target), pick the right model tier, and rule on agents that run past it. Use whenever delegating work to subagents, launching a Workflow, deciding how to split a task across agents, or handling a watchdog alert about a full context.
    4 repo stars
  68. ▌
    Worktrees 2 · seasonedcc
    Run parallel tasks in isolated git worktrees, each with its own databases, ports, env files, and dev server. Use when creating or removing worktrees, running parallel tasks or agents, starting a dev server for a specific worktree, running browser tests against an isolated server, or when the user mentions worktree, parallel lanes, or isolated environments.
    4 repo stars
  69. ▌
    Worktrees 3 · seasonedcc
    Run parallel tasks in isolated git worktrees, each with its own databases, ports, env files, and dev server. Use when creating or removing worktrees, running parallel tasks or agents, starting a dev server for a specific worktree, running browser tests against an isolated server, or when the user mentions worktree, parallel lanes, or isolated environments.
    4 repo stars
  70. ▌
    Worktrees 4 · seasonedcc bundle
    Run parallel tasks in isolated git worktrees, one per workspace repo being changed, provisioned by the setup/teardown scripts (env files, databases, ports for product-monolith). Use when creating or removing worktrees, running parallel tasks or agents, starting a dev server for a specific lane, or when the user mentions worktree, parallel lanes, or isolated environments.
    4 repo stars
  71. ▌
    MCP Server 2 · seasonedcc
    Extend and maintain the app's MCP server — add tools for new or existing app capabilities, keep the CI parity check green, and work with the OAuth 2.1 layer. Use when adding or changing any business function or route (the parity test will demand MCP coverage), when writing MCP tools, when working on app/mcp/, the /mcp endpoint, OAuth routes, scopes, or the consent screen, or when the user mentions MCP, tools, or the parity check.
    4 repo stars
  72. ▌
    MCP Server 3 · seasonedcc
    Build and extend the app MCP server — the machine surface that exposes app capabilities as tools over OAuth 2.1. Use when adding or changing an MCP tool, wiring a new domain into the MCP server, touching app/mcp/*, the oauth business layer, or the /mcp, /oauth/*, or /.well-known/* routes, when working on the parity check or pending-coverage, or when the user mentions MCP, tools, Model Context Protocol, OAuth, bearer tokens, scopes, or the consent screen.
    4 repo stars
  73. ▌
    Release 4 · seasonedcc
    Cut a release — scope the span since the last release, deeply study every merged pull request in it, write release notes in which every sentence traces to a merged change, run the gates and audits, and treat the publish as the deliberate final act. Use when the user asks to release, cut a release, publish, ship a new version, ship what's on main, release to production, or write release notes.
    4 repo stars
  74. ▌
    Shaping 2 · seasonedcc
    Run framing and shaping sessions that end in a shaping document, and answer questions about the method from the verbatim books and posts in references/. Use when framing a raw idea, shaping a project, writing or revising a shaping document under shaping/, working feedback on one back in, breadboarding or drawing fat marker sketches, finding and defusing time bombs (Shape Up's rabbit holes), naming no-gos, or when reasoning about customer demand — jobs to be done, JTBD, the struggling moment, forces of progress, demand-side selling, why people switch. Also the corpus to consult on anything Shape Up covers beyond our process — pitches, appetite, betting tables, scopes, hill charts, scope hammering, deciding when to stop.
    4 repo stars
  75. ▌
    Testing 4 · seasonedcc
    Write, run, and debug tests across the project's unit and end-to-end suites. Covers test-driven development and mutation proofs, gate reconciliation, parallel-safe unit tests, E2E seeding and retry safety, coverage discipline, and diagnosing CI-only failures and flakes. Use when writing tests, fixing or diagnosing failing or flaky tests, running test suites, seeding E2E data, or when the user mentions testing, test-driven development, unit tests, E2E tests, or mutation proofs.
    4 repo stars
  76. ▌
    Release 5 · seasonedcc
    Cut a release — scope the span since the last release, deeply study every merged pull request in it, write release notes in which every sentence traces to a merged change, run the gates and audits, and treat the publish as the deliberate final act. Use when the user asks to release, cut a release, publish, ship a new version, ship what's on main, release to production, or write release notes.
    4 repo stars
  77. ▌
    Testing 5 · seasonedcc bundle
    Write, run, and debug tests across the project's unit and end-to-end suites. Covers test-driven development and mutation proofs, gate reconciliation, parallel-safe unit tests, E2E seeding and retry safety, coverage discipline, and diagnosing CI-only failures and flakes. Use when writing tests, fixing or diagnosing failing or flaky tests, running test suites, seeding E2E data, or when the user mentions testing, test-driven development, unit tests, E2E tests, or mutation proofs.
    4 repo stars
  78. ▌
    Type Safety 2 · seasonedcc
    Write minimal, correct TypeScript type annotations. Use when adding types, declaring variables, writing function signatures, creating type aliases, or reviewing code for unnecessary type declarations.
    4 repo stars
  79. ▌
    Reground 2 · seasonedcc
    Reground after a compaction — from this session's ledger and the real sources of truth, never from the compacted summary alone. Use ONLY when the user explicitly invokes /reground — the person types this command, never you.
    4 repo stars
  80. ▌
    Quick 5 · seasonedcc
    Run a small fix or polish to an existing surface under a reduced quick-iteration Definition of Done — no subagents, no self-improvement pass. Use ONLY when the user explicitly invokes /quick; never select this mode on your own, never suggest it, and never let it self-trigger.
    4 repo stars
  81. ▌
    Env Vars 3 · seasonedcc
    Manage environment variables following the two-tier env pattern. Use when adding new env vars, modifying env schemas, working with app/framework/env.server.ts or app/env.server.ts, or updating CI env configuration.
    4 repo stars
  82. ▌
    Demo Videos 2 · seasonedcc
    Produce the two narrated demo videos for a scope of work — a five-minute highlights cut and a full-length walkthrough — filmed from a screenplay against the seeded product. Use when the user invokes /demo-videos, asks for a demo video, demo videos, a screencast, a product walkthrough video, a narrated demo, video narration, a recording of what shipped, or a video to show stakeholders what a project delivered.
    4 repo stars
  83. ▌
    Post Review 2 · seasonedcc
    Post a completed code review on a teammate's GitHub PR as inline comments anchored to the diff, with the verdict and blocking rationale in the review summary. Use when posting review findings to GitHub, requesting changes or approving a PR, taking over a PR by the founder, or after analyzing a PR (the pr-review skill covers the analysis) when the findings should land on the PR itself.
    4 repo stars
  84. ▌
    Main Sync 3 · seasonedcc
    Sync a long-lived feature branch with its repo's advancing main — bring main's commits into the branch under the repository's sync strategy, judge the rule-set and capability deltas, and re-run the combined Definition of Done. Use when main gains commits under a goal or review-fixes feature branch, before syncing a feature branch with origin/main, or when deciding whether a feature landed on main must be mirrored on the branch.
    4 repo stars
  85. ▌
    Pr Review 3 · seasonedcc
    Review a GitHub pull request with full context — the description, every comment, review, and inline thread, then the diff — judging the big picture personally before multi-angle finding and adversarial verification. Use when asked to review a PR, analyze a pull request, assess a teammate's changes, or run the pre-merge adversarial review of a draft PR; use this instead of the native /review command.
    4 repo stars
  86. ▌
    Subagents 5 · seasonedcc
    Spawn subagents and dynamic workflows well — size each task to the context window (~33% of 1M target), pick the right model tier, and rule on agents that run past it. Use whenever delegating work to subagents, launching a Workflow, deciding how to split a task across agents, or handling a watchdog alert about a full context.
    4 repo stars
  87. ▌
    Worktrees 5 · seasonedcc
    Run parallel tasks in isolated git worktrees, each provisioned as a lane with its own databases, ports, env files, and services through the seasoned-skills binary. Use when creating or removing worktrees, provisioning or tearing down lanes, running parallel tasks or agents, starting a dev server for a specific lane, handing a lane to the user for manual testing, or when the user mentions worktree, parallel lanes, or isolated environments.
    4 repo stars
  88. ▌
    Review Fixes 2 · seasonedcc
    Turn a completed PR review's findings into an adjudicated fix scope and land the fixes on the reviewed PR's own branch — triage the certain defects, adjudicate everything else with the user one finding at a time, then orchestrate fix lanes merged into the feature branch. Use when fixing review findings on our own PR, addressing a pr-review analysis, or driving a reviewed PR toward a clean re-review.
    4 repo stars
  89. ▌
    Authorization 2 · seasonedcc
    Implement authorization using context getters, context schemas, and composable functions. Use when working with authentication, permissions, user access control, protected routes, business logic authorization, or when user mentions auth, context, permissions, or access control.
    4 repo stars
  90. ▌
    Authorization 3 · seasonedcc
    Implement authorization using context getters, context schemas, and composable functions. Use when working with authentication, permissions, user access control, protected routes, business logic authorization, or when user mentions auth, context, permissions, or access control.
    4 repo stars
  91. ▌
    Nested Routes 2 · seasonedcc
    Create nested route sections with layouts, index redirects, and menu navigation in React Router v7. Use when adding new route groups, creating layouts with sidebar navigation, nesting routes under a parent path, or restructuring flat routes into nested ones.
    4 repo stars
  92. ▌
    Optimistic UI 2 · seasonedcc
    Build optimistic UI with React Router using deterministic resource routes. Use when implementing toggles, optimistic updates, action-only routes, or when user mentions optimistic UI, toggle, or real-time feedback.
    4 repo stars
  93. ▌
    Optimistic UI 3 · seasonedcc
    Build optimistic UI with React Router v7 using deterministic resource routes. Use when implementing toggles, optimistic updates, action-only routes, or when user mentions optimistic UI, toggle, or real-time feedback.
    4 repo stars
  94. ▌
    Kysely 5 · seasonedcc
    Write Kysely queries and migrations following project conventions. Use when writing migrations, creating tables, adding columns, creating enums, writing database queries with Kysely, or using database transactions.
    4 repo stars
  95. ▌
    Agent Browser 2 · seasonedcc bundle
    Automate browser interactions using the agent-browser CLI. Use when navigating pages, clicking elements, filling forms, taking screenshots, extracting page data, running browser tests, or verifying UI behavior. Use when the user mentions browser, agent-browser, test in browser, navigate, click, screenshot, interact with page, or automate.
    4 repo stars
  96. ▌
    Agent Browser 3 · seasonedcc bundle
    Automate browser interactions using the agent-browser CLI, and keep its sessions and processes from leaking. Use when navigating pages, clicking elements, filling forms, taking screenshots, extracting page data, running browser tests, verifying UI behavior, or cleaning up leftover browser processes. Use when the user mentions browser, agent-browser, test in browser, navigate, click, screenshot, interact with page, automate, leaked or runaway browsers, Chrome eating memory, or killing processes.
    4 repo stars
  97. ▌
    Agent Browser 4 · seasonedcc bundle
    Automate browser interactions using the agent-browser CLI. Use when navigating pages, clicking elements, filling forms, taking screenshots, extracting page data, running browser tests, or verifying UI behavior. Use when the user mentions browser, agent-browser, test in browser, navigate, click, screenshot, interact with page, or automate.
    4 repo stars
  98. ▌
    Design System 2 · seasonedcc
    Follow the app's design system when building or changing UI. Use when creating pages, lists, forms, drawers, modals, badges, buttons, empty states, headings, or status indicators, when choosing icons or copy, or when the user mentions design system, UI patterns, visual consistency, typography, or UX canon.
    4 repo stars
  99. ▌
    Design System 3 · seasonedcc
    Follow the app design system when building or changing UI. Use when creating pages, lists, forms, drawers, modals, badges, buttons, empty states, headings, or status indicators, when choosing icons, copy, button sizes, or breakpoints, when making a surface work on phones, tablets, or paper, or when the user mentions design system, UI patterns, visual consistency, typography, responsiveness, mobile, printing, or UX canon.
    4 repo stars
  100. ▌
    Orchestration 2 · seasonedcc
    Run delegated work reliably — writing subagent charters, verifying subagent claims, keeping judgment at the orchestrator tier, ledger discipline, recovering from interruptions, and shipping/merging lane PRs. Use when spawning subagents or workflows, coordinating parallel lanes, resuming after a session limit or compaction, or rebasing and merging a lane's PR. The subagents skill covers task sizing and model choice; this skill covers everything after the spawn.
    4 repo stars