@luizsantiago/agentic-fullstack

Full Stack Floor Map companion for Spec Seatbelt — Floors layer Execute manuals plus a specialist skill catalog. Progressive loading, one layer per task.


Keywords
ai, agent, cursor, claude, spec-driven, seatbelt, floors, fullstack, frontend, backend, data, analytics, cli, agent-skills, ai-agents, ai-coding, claude-code, developer-tools, fullstack-development, nodejs, npm-package, path-domains, spec-driven-development, spec-guardrails, tech-atlas, token-efficiency
License
MIT
Install
npm install @luizsantiago/agentic-fullstack@0.4.0

Documentation

Tech Atlas

npm version license: MIT

Pre-1.0: APIs and Path Domain ids may change before 1.0. Prefer pinning a minor version in CI.

Tech Atlas routes the minimum relevant tech engineering context to each AI agent task — Path Domain manuals + an optional specialist catalog.

npm: @luizsantiago/tech-atlas 0.5.0 (transition aliases: fullstack-floor-map, agentic-fullstack).

Claim (honest): Tech Atlas provides a structured, explainable, progressively loaded method for selecting the minimum relevant tech engineering context for an AI agent task. It does not guarantee that the correct context is always selected.

Tagline: Route the minimum relevant tech engineering context to each AI agent task.

Atlas family

Atlas packages specialize AI agents in a domain. Tech Atlas is the first (tech engineering). Future Atlases (e.g. marketing, content) may follow the same pattern. Only this package ships now.

Each Atlas works solo or paired (Lego) with Spec Guardrails — Guardrails stays a complete product on its own.

Desks (.specs/desks/) remain planned — not shipped as delivered runtime in 0.5.0.


Solo vs paired (Lego)

Mode Spec Guardrails What works
Solo Not required install (warn only), doctor (warn), route, validate-domains, PROJECT.md, catalog
Paired @luizsantiago/spec-guardrails ≥3 Gate also under .specs/guardrails/scripts/; Execute = Guardrails + 1 Path Domain + ≤1 specialist; Verify = Guardrails only

Spec Guardrails owns spec, tasks, process gates, and /verify. Tech Atlas owns Path Domains, routing gate, catalog, and (planned) Desks. Do not reimplement Verify inside Atlas.


Install

In your product repository (Node.js 18+. Python 3.10+ for gates):

Paired (recommended):

npx @luizsantiago/spec-guardrails install
npx @luizsantiago/tech-atlas install
npx @luizsantiago/tech-atlas doctor

Solo:

npx @luizsantiago/tech-atlas install
npx @luizsantiago/tech-atlas doctor

What install does

Lands in your project Purpose
.cursor/skills/*-engineering.md (+ .claude/) Path Domain manuals
.cursor/skills/<specialist>/ Specialist catalog (SKILL.md + references/)
.cursor/rules/tech-atlas.mdc One Path Domain + at most one specialist
.specs/tech-atlas/scripts/validate_layer_routing.py Routing gate (Atlas-owned; always)
.specs/companions/INDEX.json Atlas family registry (written on install)
.specs/guardrails/scripts/validate_tech_atlas_routing.py Namespaced gate mirror when paired
.specs/project/PROJECT.md Stack + Path Domain registry (created if missing)
Need Command
Skills without Guardrails install (solo — no --force required)
Refresh registry globs only install --sync-registry
Check health doctor
Check task Files vs domains validate-domains <feature>
Explain context for a task route --feature … --task …

How the pieces fit together

Idea Package Role
Guardrails @luizsantiago/spec-guardrails Spec, tasks, gates, Verify
Path Domain this package Which code room a task lives in
Specialists catalog in this package Framework craft — load on demand
Desk this package (planned 0.5.0) Specialist memory / continuity

Pairing: keep the feature vertical (one user path). Split tasks by Path Domain — never mix apps/web and apps/api in one Files list.

Execute load (paired): Guardrails working set + one *-engineering.md + at most one specialist SKILL.md + ≤2 craft references/.
Verify: Guardrails only — no Path Domain manuals, no catalog specialists.

Ownership: Companion: Spec Guardrails.


Documentation

Guide Topic
Quick start Install → registry → validate-layers → Execute
Concepts Path Domains, pairing, load policy
Six Path Domains Domain manuals (web, mobile, backend, data, ml, infra)
Specialist catalog 67 skills, install ≠ load
Layer routing gate Gate paths & CLI
Companion: Spec Guardrails Pairing contract / ownership
Companion Sync Keep Guardrails docs in sync
Companion Sync prompt Paste into a Guardrails-only agent
CLI Commands
FAQ Common questions
Migration 0.4 → 0.5 Tech Atlas
Credits Attribution

Credits

This package adapts open ideas; Path Domain routing is original here.

Source License How we use it
jeffallan/claude-skills MIT Specialist catalog (SKILL.md + references/)
spec-guardrails MIT Companion pairing, guide shape, Verify ownership

Extended attribution: docs/guide/credits.md · NOTICE

License

MIT