beskars-code
- 18 skills
- 0 followers
- 19 hours ago last updated
- ▌ Task · beskars-code bundleStateless end-to-end build loop: grill, plan, implement, gather acceptance evidence, and review one verifiable outcome using in-chat execution context. Use when the user wants a feature or outcome built end to end. Nested under /just-do-it when that parent owns shipping.
- ▌ Taste · beskars-code bundlePack coding taste: keep it simple, keep jobs apart, honest names, fail fast, trust the server, types tell the truth, don’t repeat yourself, and related rules. Use to audit or apply taste to a lane; parents load it before planning or writing code.
- ▌ Design · beskars-code bundleDesigner and customer-experience worker for user-facing UI. Owns docs/design.md (the app UX source of truth), captures the app from code, and implements screens, components, and visible copy to a finished professional bar in one pass. Use when building frontend, initializing or updating design.md, or the user talks about UX, clicks, keystrokes, or how a screen should feel.
- ▌ Analyze · beskars-code bundleStateless task analysis returned in chat. One-off research with promote-to-task handoffs, or nested under a parent (write-ticket, just-do-it, review remediation). Does not write tickets or automatic artifacts.
- ▌ Publish · beskars-code bundlePublish completed work on a typed branch and optionally open a GitHub PR. Uses an approved draft with concrete QA steps and a high-level Mermaid Change diagram (Before/After for rework). Any agent that opens a PR follows the same ship contract, not only this skill. Use after work is complete when the user wants to ship a branch or PR. Never use inside /task.
- ▌ Grill Me · beskars-code bundleRelentless stateless interview that sharpens intent through batched questions and a Locked closure in chat. Keeps decisions and Active Rules in shared execution context. User must invoke (not auto).
- ▌ Trackers · beskars-codeRead-only Linear/GitHub ticket and PR context for specifications and acceptance criteria. Used by parent orchestrators and never writes to trackers.
- ▌ Implement · beskars-codeImplement one bounded worker slice from the parent’s inline execution context.
- ▌ Pr Review · beskars-code bundleStateless review of an open GitHub PR. Standards hard-require /taste KISS + named principles (including honest names, trust the server, types tell the truth, and naming alignment) and /architecture, plus a correctness hunt and PR extras (body vs diff, migrations, breaking API). Triage historical finding threads, draft one-topic comments, post only after one publish decision.
- ▌ Just Do It · beskars-code bundleAutonomously turn a Linear ticket into a typed branch, reviewed implementation, and visible GitHub PR. Carries safety and review state in chat execution context. Use when the user wants ticket-to-PR execution.
- ▌ Split Task · beskars-codeSplit a bounded outcome into small, ordered inline slice contracts in shared execution context for a parent orchestrator.
- ▌ Ask Gabriel · beskars-codeThin router over this pack: recommend which skill to run next. Sole auto-invokable skill. Use when unsure which skill, what to run next, before non-trivial work, after a phase completes, when multiple pack skills could apply, or the user asks what to do. Agents should reach for this often.
- ▌ Code Review · beskars-code bundleReview a shipped diff for quality and whether it matches the request. Quality checks use /taste and /architecture (keep it simple, keep jobs apart, honest names, trust the server, types tell the truth, and related rules), a correctness hunt for reachable bugs, plus a pass for stale file and symbol names after renames. Parallel Standards and Spec Tasks, evidence-backed findings, and a bounded fix path. Use for branch, PR, or parent-owned review. User must invoke (not auto).
- ▌ Create Test · beskars-code bundleWrite durable behavior-lock tests for complex hooks, domain logic, facades, and stateful classes. User-invoked skill, used only after /code-review or /pr-review recommends a lock—not for coverage theater.
- ▌ Pack Shared · beskars-code bundleInternal pack contracts for Gabriel Lafrance Skills: asking, stateless execution context, subagent dispatch, review behavior, and how every agent opens a PR. Not user-invoked. Other skills link here so shared docs install with npx skills (skill folders only).
- ▌ Architecture · beskars-code bundleShape scalable code: one service per domain job, simple public APIs, one-job helpers inside those services, writes that check who may act, clear folders, cheap honest reads, and writes that are safe to retry. Use to decide structure, or inside /task before planning. Triggers: folders, services, split logic, data/reads, duplicating domain logic, auth on writes, Date.now in queries.
- ▌ Write Ticket · beskars-code bundleCreate or refine one Feature, Tweak, Bug, Refactor, Chore, or Hotfix ticket from a single prompt. Infers type and body, always runs full /analyze, and asks only a too-short grill or missing tracker metadata. Use for Linear or GitHub tickets, including “don’t forget this” captures; never inside /task.
- ▌ Setup Toolkit · beskars-code bundleInstall ESLint, Prettier, Cursor/VS Code workspace files, and principle quality-gate tests into the current JavaScript or TypeScript repo from this pack's templates. Also starts docs/design.md capture when that file is missing. Use when the user wants linting, formatting, ESLint, Prettier, a formatter, recommended extensions, a complexity test, test:quality, dead code, Knip, mutants, Stryker, test:mutants, design.md, or to add the engineering toolkit to an app. Bans em dashes. Not for rewriting an existing lint stack.