Stack Baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability, with the chosen default + the one sanctioned alternative for each. Applied whenever a new product is scaffolded or a stack choice would otherwise be improvised. Re-deciding the stack every build is the biggest silent time sink; this kills it.
Install
npx skills add jeremybrasher/grokbot-skills --skill stack-baselinegit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/stack-baseline ~/.claude/skills/stack-baselinePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Stack baseline — decide once, build on it Every SMB product builds on the SAME proven stack unless there's a concrete reason not to. Re-deciding framework/ORM/auth/host per build wastes the first hour of every project and fragments the codebase across products. **This is the default; deviate only with a written reason in ARCH.** ## The pinned stack | Layer | Default | Sanctioned alternative | Notes | |---|---|---|---| | **Framework** | Next.js (App Router, TS) | Remix | Server actions + RSC; one repo front+back | | **UI** | Tailwind + shadcn/ui | — | matches the site; design-advisor tokens map to it | | **Charts** (dashboard/analytics) | ECharts (shipped) | Recharts | polished specs generated at **build time via Flint → compiled to native ECharts**; Flint is dev-only, never a runtime dep. Contract: `references/dashboard-viz.md` | | **DB** | Postgres | — | the only DB; integer cents, tz-aware timestamps | | **ORM / migrations** | Drizzle | Prisma | typed schema + SQL migrations; migration-ready-schema applies | | **Auth** | Auth.js (NextAuth v5) | Clerk (fast path, per-MAU cost) | owned by **auth-engineer**; session + RBAC + multi-tenant | | **Payments** | Stripe (+ Connect) | — | owned by subscription-billing-engineer / integrations-engineer | | **Email** | Resend | Postmark | transactional; SPF/DKIM/DMARC via lifecycle-messaging | | **SMS** | Twilio (Messaging Service) | Telnyx | 10DLC; consent via lifecycle-messaging |
Details
- Skill name
stack-baseline- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/stack-baseline/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Stack Baseline skill do?
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability, with the chosen default + the one sanctioned alternative for each. Applied whenever a new product is scaffolded or a stack choice would otherwise be improvised. Re-deciding the stack every build is the biggest silent time sink; this kills it.
How do I install the Stack Baseline skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill stack-baseline. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Stack Baseline popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Test Strategy
38jeremybrasher/grokbot-skills
Coverage-design method for qa-engineer — pyramid ratios per archetype, equivalence/boundary/property case selection, mutation score as the real coverage signal, and a flake-quarantine policy. Turns "coverage is 90%" (a number with no method) into a defensible test plan. Emits TEST-STRATEGY-{slug}.md, which the QA gate checks exists.
Wcag Audit
48sethdford/claude-skills
Expert approach to wcag-audit in accessibility testing. Use when working with .
A B Testing Framework
39lionelsimai/claude-skills-collection
Build A/B testing frameworks for features. TRIGGERS - Use when user needs help with a-b-testing-framework related tasks.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.