Agent skill

Stack Baseline

by avelikiy in avelikiy/great_cto

The pinned default technology stack for SMB Product-Builder products.

MITAuto-check passedDatabases

Install Stack Baseline

skills CLI
$ npx skills add avelikiy/great_cto --skill stack-baseline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avelikiy/great_cto stack-baseline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/stack-baseline .claude/skills/stack-baseline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stack-baseline
GitHub stars
103
Token cost
~1.1k tokens
SKILL.md length
341 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

The pinned default technology stack for SMB Product-Builder products.

  • Works in 5 steps: One framework, one DB, one ORM, one auth… → Pin it in .great_cto/PROJECT.md at… → Money in integer cents; timestamps… → …
  • Tasks that involve ORMs and data access
  • SKILL.md covers The pinned stack, Rules and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stack Baseline is an agent skill from avelikiy/great_cto. 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…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering ORMs and data access, Project scaffolding and Observability. The repository describes itself as: You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next… The licence is MIT.

When your agent uses it

  • Tasks that involve ORMs and data access
  • Tasks that involve Project scaffolding
  • Tasks that involve Observability

Example prompts

  • “/stack-baseline”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Grep, Glob

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. One framework, one DB, one ORM, one auth lib across all products. Consistency >
  2. Pin it in .great_cto/PROJECT.md at scaffold time (stack: line) so every later
  3. Money in integer cents; timestamps tz-aware; IDs are stable (compose with
  4. Auth, payments, email/SMS, jobs are owned by their specialist (auth-engineer,
  5. Deviation needs a written reason in ARCH's Components section (e.g. "Clerk over Auth.js

What it can do on your machine

Read from SKILL.md and the folder at commit 0658773. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stack Baseline loads about 1.1k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 341 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from avelikiy/great_cto at commit 0658773, republished under its MIT licence (© avelikiy). 341 words, ~1,072 tokens.

Download SKILL.mdSave it as .claude/skills/stack-baseline/SKILL.md (or your agent's skills folder).
name
stack-baseline
description
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.
allowed-tools
Read, Write, Grep, Glob
when_to_use
Apply when: - architect writes the Components / stack section of ARCH-{slug}.md - app-scaffolder stands up a new product skeleton - auth-engineer or…
effort
low
paths
docs/architecture/**, docs/plans/**, .great_cto/**

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>

© avelikiy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/stack-baseline of avelikiy/great_cto.

Open the folder on GitHubat commit 0658773

Compare with similar skills

Stack Baseline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stack Baseline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stack Baseline this skillavelikiy/great_cto103—~1.1kAutomated safety check: PassMIT
Backend Dev Guidelineslangfuse/langfuse35k—~1.9kAutomated safety check: PassCustom licence
Add Componentlbedner/aegis-stack143—~5.3kAutomated safety check: PassMIT
AWS Harnesshoodini/ai-agents-skills282—~4.2kAutomated safety check: NotesNone
Agent Observability Experiment Bootstrapdatadog-labs/agent-skills177—~2.3kAutomated safety check: PassMIT
Otel Weaverollygarden/opentelemetry-agent-skills106—~2.7kAutomated safety check: PassApache-2.0

Similar skills

  • Backend Dev Guidelines

    langfuse/langfuse

    Build or review Langfuse backend code. An agent skill from langfuse/langfuse.

    35k GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed
  • Add Component

    lbedner/aegis-stack

    A skill your agent uses when adding a new infrastructure component (worker, scheduler, database, redis, ingress, observability) to the Aegis Stack framework itself, or adding a new variant axis…

    143 GitHub stars~5.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • AWS Harness

    hoodini/ai-agents-skills

    Build a new AI agent on AWS and deploy it easily, OR wrap and deploy an agent you already have, using the Amazon Bedrock AgentCore harness.

    282 GitHub stars~4.2k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes
  • Bootstrap a reproducible LLM Observability experiment through the Python ddtrace SDK or the Node dd-trace SDK.

    177 GitHub stars~2.3k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • Otel Weaver

    ollygarden/opentelemetry-agent-skills

    OpenTelemetry Weaver registry authoring, codegen, and CI enforcement.

    106 GitHub stars~2.7k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • Inspect an application repository connected to PlanetScale and recommend SQLCommenter-compatible query tagging packages and conventions.

    132 GitHub stars~1.2k tokensUpdated 4 days ago
    DatabasesAuto-check passed

More from avelikiy/great_cto

All 30 skills in this repo
  • AnyDesign Design Analyzer

    avelikiy/great_cto

    Analyzes a screenshot, website or Figma file and writes a `design.md` with its token system, component inventory and reconstruction notes, or an `element.md` for one element.

    103 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Opportunity Solution Tree

    avelikiy/great_cto

    Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.

    103 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.

    103 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Exposed Secret Rotation

    avelikiy/great_cto

    Turns a leaked key, token or password into one tracked rotation task the moment it's spotted, instead of a reminder repeated every session.

    103 GitHub stars~884 tokensUpdated yesterday
    Auto-check: notes
  • Decision Eval

    avelikiy/great_cto

    Spawns the decision-scorer agent after architect proposes 2+ variants in an ADR.

    103 GitHub starsUsed in 1 repo~884 tokens
    Auto-check: notes
  • Skeptical Triage

    avelikiy/great_cto

    Runs a three-round self-challenge plus an arbiter over high-stakes findings, so false positives from reviews, audits and flaky-test verdicts do not become blockers.

    103 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check: notes

Questions about Stack Baseline

What does Stack Baseline do?

The pinned default technology stack for SMB Product-Builder products. Stack Baseline is an agent skill from avelikiy/great_cto. The pinned default technology stack for SMB Product-Builder products.

When should I use Stack Baseline?

Stack Baseline fits situations like: tasks that involve ORMs and data access; tasks that involve Project scaffolding; tasks that involve Observability.

How do I install Stack Baseline in Claude Code?

Run `npx skills add avelikiy/great_cto --skill stack-baseline -a claude-code`. Or copy the skill folder (skills/stack-baseline in avelikiy/great_cto) into .claude/skills/stack-baseline in your project. Claude Code loads it when a task matches its description.

How do I install Stack Baseline in Codex?

Run `npx skills add avelikiy/great_cto --skill stack-baseline -a codex`. Or copy the skill folder (skills/stack-baseline in avelikiy/great_cto) into .agents/skills/stack-baseline in your project. Codex loads it when a task matches its description.

Can I use Stack Baseline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avelikiy/great_cto --skill stack-baseline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stack-baseline, .gemini/skills/stack-baseline, .github/skills/stack-baseline and .opencode/skills/stack-baseline in your project.

What does Stack Baseline need to run?

SKILL.md names no scripts, command-line tools or credentials: Stack Baseline is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Grep, Glob.

Does Stack Baseline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stack Baseline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stack Baseline use?

Stack Baseline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stack Baseline use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stack Baseline?

Skills that share tags, products or a category with Stack Baseline: Backend Dev Guidelines (langfuse/langfuse, 35k stars), Add Component (lbedner/aegis-stack, 143 stars), AWS Harness (hoodini/ai-agents-skills, 282 stars) and Agent Observability Experiment Bootstrap (datadog-labs/agent-skills, 177 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stack Baseline?

avelikiy (a GitHub user) maintains it in avelikiy/great_cto, which has 103 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 6, 2026.

Source: avelikiy/great_cto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.