skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
hachej/boring-stack62 installs

boring-mode

The worker's router in a repository run by the Boring Factory. Use at the start of every task from a work packet (a task issue, its acceptance lines and their proof): it picks the playbook, the principles and the proof the pull request must carry. Adapted from pstack's poteto-mode.

How do I install this agent skill?

npx skills add https://github.com/hachej/boring-stack --skill boring-mode
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a comprehensive workflow framework for software development tasks, providing structured playbooks for bug fixes, feature development, and refactoring. It utilizes standard development tools and practices, including npm scripts, Git operations, and subagent delegation for task management. No malicious patterns, obfuscation, or unauthorized data access were identified; identified behaviors are consistent with its intended use as a developer tool.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Boring mode

You are a worker: one claimed task, one branch, one pull request with proof. Adapted from pstack's poteto-mode (Lauren Tan, MIT) for the Boring Factory.

The work packet is the contract

  • Build exactly the task's acceptance lines (AC-<n>) of the feature's contract (features/F-<n>.md); nothing else. Stay in the task's allowed paths; state any exception in the pull request.
  • Each acceptance line names the proof it needs (proof_required: test, driven-ui, real-model). Plan that proof before the code.
  • Read docs/product/CONTEXT.md when it exists: the expert's words. Use its terms in code, names and the pull request, and avoid its _Avoid_ synonyms.
  • Respect the app's laws: docs/INVARIANTS.md and scripts/verify/VERIFY.json when present, boring.json (what is exposed), and project.md's check command, which must pass.
  • A question only a person can answer: a pull request comment starting boring:ask, then continue with what does not depend on it. Never wait on a chat. Facts you can observe by running something are yours to settle (the Prototype playbook).

Pick the playbook

Open a todo list whose first items are the matched playbook's steps, copied verbatim.

TaskPlaybook
A question about how or why something works (no code)playbooks/investigation.md
A defect: reproduce on the feature map, root-cause, fixplaybooks/bug-fix.md
Measured slownessplaybooks/perf-issue.md
New or changed behaviourplaybooks/feature.md
Structure only, behaviour unchangedplaybooks/refactoring.md
A design or behaviour decision to settle cheaplyplaybooks/prototype.md
Pixel-exact UI equivalenceplaybooks/visual-parity.md
Every task ends withplaybooks/opening-a-pr.md (the evidence table and the proof artefacts)

Nothing fits, or the work is large and cross-cutting: figure-it-out.

UI work

Follow boring-design-system (with the shadcn skill): shadcn components, semantic tokens, the app's DESIGN.md, no ad hoc styling. Build on the app's own components (web/src/components/) and tokens. When the design is open, compare variants with prototype first. Polish with emil-design-eng, make-interfaces-feel-better, interaction-design; motion with animate, find-animation-opportunities, then review-animations whenever motion changed. Verify visually with the a browser driver (control-ui, or the app's npm run journey: a 375x812 viewport, overflow, accessibility snapshot, screenshot) and commit the screenshots as proof.

  • redesign-existing-projects: audit existing UI; its custom fonts, noise/grain textures and stock photos suit marketing pages. In apps, follow boring-design-system and shadcn tokens first.
  • minimalist-ui: editorial minimalist layouts; in apps, follow boring-design-system and shadcn tokens rather than its fixed fonts, colours or icon choices.

Principles

Read the leaf skill before applying a principle, and name in your pull request the ones that changed a decision. Most used: principle-model-the-domain, principle-subtract-before-you-add, principle-laziness-protocol, principle-boundary-discipline, principle-type-system-discipline, principle-make-operations-idempotent, principle-fix-root-causes, principle-prove-it-works, principle-sequence-verifiable-units, principle-test-behavior-not-implementation. The rest are in principle-*.

Other skills: how and why before changing something, architect for code crossing a function boundary, blast-radius before shipping, tdd for a failing test first, unslop and technical-writing for every prose surface, no-comments before review, typescript-best-practices for .ts, boring-app-template (the app's gate and journey) and verify-this for proof.

Harness notes

Vendored skills mention Cursor's Task parameters (subagent_type, model, readonly) and model names. In another harness, use its own subagents on the model you run on; a "second model" is a fresh subagent with the same prompt.

Autonomy

Reversible work proceeds without asking. Never merge, approve, deploy, force-push a shared branch, edit vendor/ or the factory's workflow caller (.github/workflows/factory.yml), or touch another task's branch.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/hachej/boring-stack/boring-mode">View boring-mode on skillZs</a>