Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto
Works withStripeVercelCloudflarePostgreSQLSentryPlaywright
See how to install

Files included (1)

  • SKILL.md4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

LayerDefaultSanctioned alternativeNotes
FrameworkNext.js (App Router, TS)RemixServer actions + RSC; one repo front+back
UITailwind + shadcn/ui—matches the site; design-advisor tokens map to it
Charts (dashboard/analytics)ECharts (shipped)Rechartspolished specs generated at build time via Flint → compiled to native ECharts; Flint is dev-only, never a runtime dep. Contract: references/dashboard-viz.md
DBPostgres—the only DB; integer cents, tz-aware timestamps
ORM / migrationsDrizzlePrismatyped schema + SQL migrations; migration-ready-schema applies
AuthAuth.js (NextAuth v5)Clerk (fast path, per-MAU cost)owned by auth-engineer; session + RBAC + multi-tenant
PaymentsStripe (+ Connect)—owned by subscription-billing-engineer / integrations-engineer
EmailResendPostmarktransactional; SPF/DKIM/DMARC via lifecycle-messaging
SMSTwilio (Messaging Service)Telnyx10DLC; consent via lifecycle-messaging
File storageCloudflare R2 / S3—private buckets, presigned URLs
Background jobsInngesta Postgres-backed queuereminders, syncs, dunning
TestingVitest (unit) + Playwright (e2e)—senior-dev unit; e2e-test-engineer browser
HostingVercelCloudflare Pages/WorkersNext.js-native; preview per PR
DB hostNeon (serverless PG)Supabasebranchable; env-wired by infra-provisioner
ObservabilitySentry—errors + traces on the deployed product
Analyticsprivacy-light (Plausible)—no heavy 3rd-party trackers

Rules

  1. One framework, one DB, one ORM, one auth lib across all products. Consistency > per-product optimization.
  2. Pin it in .great_cto/PROJECT.md at scaffold time (stack: line) so every later agent reads it instead of guessing — and an existing PROJECT.md's stack always wins.
  3. Money in integer cents; timestamps tz-aware; IDs are stable (compose with migration-ready-schema).
  4. Auth, payments, email/SMS, jobs are owned by their specialist (auth-engineer, billing/integrations, lifecycle-messaging) — this skill only names the default library; the specialist owns the contract.
  5. Deviation needs a written reason in ARCH's Components section (e.g. "Clerk over Auth.js because the customer needs SSO/SCIM on day one").

Output

When applied, write the stack into ARCH's Components section and PROJECT.md:

## Stack (baseline)
framework: Next.js (App Router, TS) · UI: Tailwind + shadcn
db: Postgres (Neon) · orm: Drizzle · auth: Auth.js (→ auth-engineer)
payments: Stripe · email: Resend · sms: Twilio · files: R2 · jobs: Inngest
test: Vitest + Playwright · host: Vercel · obs: Sentry
deviations: <none | reason>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

aesthetic-instrument

Free

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto103Updated Oct 20, 2026

anti-patterns

Free

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).

The English summary is being prepared. Showing the original description.

avelikiy/great_cto103Updated Oct 20, 2026

anydesign

Free

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 this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto103Updated Oct 20, 2026

archetype-review-base

Free

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.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto103Updated Oct 20, 2026

brainstorming

Free

Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto103Updated Oct 20, 2026

codex-host

Free

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto103Updated Oct 20, 2026

See all skills by avelikiy

Report a problem with this skill