EasyPlatform scaffold

[Architecture] Scaffold project architecture with OOP/SOLID base classes, infrastructure abstractions, and reusable foundation code before feature implementation.

install

source · Clone the upstream repo

git clone https://github.com/duc01226/EasyPlatform

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/duc01226/EasyPlatform "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/scaffold" ~/.claude/skills/duc01226-easyplatform-scaffold && rm -rf "$T"

manifest: .claude/skills/scaffold/SKILL.md

source content

[IMPORTANT] Use
TaskCreate
to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

AI Mistake Prevention — Failure modes to avoid on every task:

Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal.

Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing.

Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain.

Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path.

When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site.

Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code.

Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks.

Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis.

Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly.

Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

Understand Code First — HARD-GATE: Do NOT write, plan, or fix until you READ existing code.
Search 3+ similar patterns (
grep
/
glob
) — cite
file:line
evidence
Read existing files in target area — understand structure, base classes, conventions
Run
python .claude/scripts/code_graph trace <file> --direction both --json
when
.code-graph/graph.db
exists
Map dependencies via
connections
or
callers_of
— know what depends on your target
Write investigation to
.ai/workspace/analysis/
for non-trivial tasks (3+ files)
Re-read analysis file before implementing — never work from memory alone

NEVER invent new patterns when existing ones work — match exactly or document deviation
BLOCKED until:
- [ ]
Read target files
- [ ]
Grep 3+ patterns
- [ ]
Graph trace (if graph.db exists)
- [ ]
Assumptions verified with evidence

Scaffold Production Readiness — Every scaffolded project MUST ATTENTION include 5 foundations:
Code Quality Tooling — linting, formatting, pre-commit hooks, CI gates. Specific tool choices →
docs/project-reference/
or
project-config.json
.
Error Handling Foundation — HTTP interceptor, error classification (4xx/5xx taxonomy), user notification, global uncaught handler.

Loading State Management — counter-based tracker (not boolean toggle), skip-token for background requests, 300ms flicker guard.
Docker Development Environment — compose profiles (
dev
/
test
/
infra
), multi-stage Dockerfile, health checks on all services, non-root production user.
Integration Points — document each outbound boundary; configure retry + circuit breaker + timeout; integration tests for happy path and failure path.
BLOCK
/cook
if any foundation is unchecked. Present 2-3 options per concern via
AskUserQuestion
before implementing.

Evidence Gate: MANDATORY IMPORTANT MUST ATTENTION — every claim, finding, and recommendation requires
file:line
proof or traced evidence with confidence percentage (>80% to act, <80% must verify first).

Quick Summary

Goal: Generate and validate the project's architecture scaffolding — all base classes, interfaces, infrastructure abstractions, and reusable foundation code — BEFORE any feature story implementation begins.

Purpose: The scaffolded project should be copy-ready as a starter template for similar projects. All base code, utilities, interfaces, and infrastructure services are created. All setup follows best practices with generic functions any feature story could reuse.

Key distinction: This is architecture infrastructure creation, NOT feature implementation. Creates the foundation layer that all stories build upon.

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Activation Guards (MANDATORY — Check Before Executing)

ALL conditions must be true to proceed:

Workflow check: Active workflow is
```
greenfield-init
```
OR
```
big-feature
```
. If not → SKIP this skill entirely, mark step as completed.
Existing scaffolding check: AI MUST ATTENTION self-investigate for existing base/foundational abstractions:
- Abstract/base classes: grep
```
abstract class.*Base|Base[A-Z]\w+|Abstract[A-Z]\w+
```
- Generic interfaces: grep
```
interface I\w+<|IGeneric|IBase
```
- Infrastructure abstractions: grep
```
IRepository|IUnitOfWork|IService|IHandler
```
- Utility/extension layers: grep
```
Extensions|Helpers|Utils|Common
```
  (directories or classes)
- Frontend foundations: grep
```
base.*component|base.*service|base.*store|abstract.*component
```
  (case-insensitive)
- DI/IoC registration: grep
```
AddScoped|AddSingleton|providers:|NgModule|@Injectable
```
If existing scaffolding found → SKIP. Log: "Existing scaffolding detected at {file:line}. Skipping /scaffold step." Mark step as completed.
If NO foundational abstractions found → PROCEED with full scaffolding workflow below.

When to Use

After the second
```
/plan
```
+
```
/plan-review
```
in greenfield-init or big-feature workflows
Before
```
/cook
```
begins implementing feature stories
When a new service/module needs its own base architecture within an existing project
NOT when the project already has established base classes and infrastructure

Workflow

Read Plan — Parse the implementation plan for architecture decisions, tech stack, and domain model
Generate Scaffolding Checklist — Produce a checklist of all required base classes and infrastructure from the Backend + Frontend checklists below
Validate Against Plan — Ensure every architecture decision in the plan has corresponding scaffolding items
Present to User — Use
```
AskUserQuestion
```
to confirm checklist before generating code
Scaffold — Create all base classes, interfaces, abstractions, and infrastructure code
Verify — Compile/build to ensure no syntax errors; validate OOP/SOLID compliance

Backend Scaffolding Categories

AI must self-investigate the chosen tech stack and produce a checklist covering these categories. Names below are illustrative — adapt to match the project's language, framework conventions, and actual needs.

Domain Layer

Base entity interface + abstract class (Id, timestamps, audit fields)
Value object base (equality by value)
Domain event interface

Application Layer

Command/query handler abstractions (CQRS if applicable)
Validation result pattern
Base DTO with mapping protocol
Pagination wrapper
Operation result pattern (success/failure)

Infrastructure Layer

Generic repository interface + one concrete implementation
Unit of work interface (if applicable)
Messaging/event bus abstraction
External service abstractions (cache, storage, email — only if plan requires them)
Database context / connection setup
DI/IoC registration module

Cross-Cutting

Current user context abstraction
Testable date/time provider
Exception hierarchy (domain, validation, not-found)
Error handling middleware
Strongly-typed configuration models

Frontend Scaffolding Categories

Core Architecture

Base component with lifecycle/destroy cleanup
Base form component with validation, dirty tracking
Base list component with pagination, sorting, filtering

State & API

Base state store with loading/error/data pattern
Base API service with interceptors, error handling
Auth interceptor + environment config

Shared Utilities

Base model with serialization helpers
Common utility functions (date, validation, formatting)

UI Foundation

Skip if: Backend-only project, no frontend component. Apply if: Project has ANY frontend.

Design Token Files

Create design token file(s) per chosen format (CSS custom properties / SCSS variables / JSON)
Define minimum token set: colors (primary, secondary, surface, bg, text, error, success, warning), spacing (xs-xl), typography (heading/body/caption families + sizes), breakpoints, shadows, z-index
Create theme file(s) if theming required (light/dark CSS classes or theme provider)

Base Layout & Responsive

Base layout component (app shell: header, sidebar/nav, main content, footer)
Responsive container/grid utility
Responsive mixin/utility for breakpoints
Mobile-first media query definitions

Base UI Components

Loading indicator component (spinner or skeleton)
Error display component (inline + page-level)
Empty state component (message + action)
Notification/toast component
Base button component with variants (primary, secondary, ghost, danger)
Base input component with validation display

Design System Documentation

Create
```
docs/project-reference/design-system/README.md
```
skeleton with: token naming conventions, component tier classification (Common/Domain-Shared/Page), usage examples (content auto-injected by hook — check for [Injected: ...] header before reading)

Code Quality Gate Tooling (MANDATORY MUST ATTENTION — Setup Before Any Feature Code)

MANDATORY IMPORTANT MUST ATTENTION scaffold ALL code quality enforcement tools as part of project infrastructure — code that passes without quality gates is technical debt from day one.

Static Analysis & Linting

MANDATORY MUST ATTENTION configure language-appropriate linter with strict ruleset (zero warnings policy on new code)
MANDATORY MUST ATTENTION configure static code analyzer with quality gate thresholds (complexity, duplication, coverage)
MANDATORY MUST ATTENTION enable compiler/transpiler strict mode and treat warnings as errors on build
MANDATORY MUST ATTENTION add code style formatter with shared config (enforce consistent formatting across team)

Build-Time Quality Enforcement

MANDATORY MUST ATTENTION configure pre-commit hooks to run linter + formatter automatically
MANDATORY MUST ATTENTION configure CI pipeline to fail on any linter violation, analyzer warning, or test failure
MANDATORY MUST ATTENTION set minimum test coverage threshold in CI (fail build if below)
MANDATORY MUST ATTENTION enable security vulnerability scanning in dependency management

Code Rules & Standards

MANDATORY MUST ATTENTION create shared linter config file at project root (team-wide consistency)
MANDATORY MUST ATTENTION create shared formatter config file at project root
MANDATORY MUST ATTENTION create
```
.editorconfig
```
for cross-IDE consistency (indentation, encoding, line endings)
MANDATORY MUST ATTENTION document code quality standards in project README or contributing guide

Adaptation Protocol

Research the chosen tech stack's ecosystem for best-in-class quality tools
Present top 2-3 options per category with pros/cons to user via
```
AskUserQuestion
```
Configure the strictest reasonable defaults — loosen only with explicit user approval
Ensure all quality tools run both locally (fast feedback) AND in CI (enforcement gate)

Production Readiness Scaffolding (MANDATORY)

Scaffold Production Readiness — See

block above for full inline protocol.

Every scaffolded project MUST ATTENTION include these 4 foundations. AI must detect the tech stack from the plan/architecture report and present 2-3 options per concern via

AskUserQuestion

1. Code Quality Tooling

Detect tech stack → select from protocol's option matrices
Generate: linter config, formatter config,
```
.editorconfig
```
, pre-commit hooks
Present options to user → generate chosen tool's config files
Run protocol's verification checklist before proceeding

2. Error Handling Foundation

Detect frontend framework → select from protocol's framework patterns
Generate: error types, HTTP interceptor, notification service, global error handler
Minimum 4 files for frontend, 3 for backend-only
Run protocol's verification checklist

3. Loading State Management

Detect frontend framework → select from protocol's framework patterns
Generate: loading service, HTTP loading interceptor, loading indicator component
Counter-based tracking, 300ms display delay, skip token mechanism
Run protocol's verification checklist

4. Docker Development Environment

Always scaffold (unless user explicitly opts out)
Generate: docker-compose.yml (with profiles), Dockerfile (multi-stage), .dockerignore, .env.example
Use 127.0.0.1 binding, health checks on all services, non-root user in prod
Run protocol's verification checklist

Scaffold Handoff from Architecture-Design

If an architecture report exists (from

/architecture-design

), read the "Scaffold Handoff — Tool Choices" table and use those selections instead of re-asking the user.

OOP/SOLID Compliance Rules (ENFORCE)

Single Responsibility — Each base class handles ONE concern
Open/Closed — Base classes are extensible via inheritance, closed for modification
Liskov Substitution — Concrete implementations are substitutable for their base
Interface Segregation — Small, focused interfaces (not one giant IService)
Dependency Inversion — All infrastructure behind interfaces, injected via DI

Anti-patterns to prevent:

God classes combining multiple concerns
Concrete dependencies (always depend on abstractions)
Base classes with unused methods that subclasses must override
Missing generic type parameters where applicable

Adaptation Protocol

The checklists above are templates. Before scaffolding:

Read the plan — What tech stack was chosen? (e.g., .NET vs Node.js, Angular vs React)
Adapt naming — Match target framework conventions (e.g., C# PascalCase, TypeScript camelCase)
Skip irrelevant items — Not every project needs every item (e.g., skip IFileStorageService if no file uploads)
Add project-specific items — The plan may require additional base classes not in the template
Use
AskUserQuestion
— Confirm final checklist with user before generating code

Output

After scaffolding is complete:

Scaffolding Report — List of all created files with brief descriptions
Build Verification — Compilation/type-check passes
Architecture Diagram — Optional: generate diagram showing the base class hierarchy
Production Readiness Verification — All 4 concern areas verified via protocol checklists
Config Files Generated — Linter, formatter, pre-commit, Docker configs all created

Verification Gate (MANDATORY before proceeding to /cook)

Run ALL verification checklists from the production readiness protocol:

Code quality tooling verified (Section 1)
Error handling foundation verified (Section 2)
Loading state management verified (Section 3)
Docker development environment verified (Section 4)

BLOCK proceeding to

/cook

if ANY verification item fails. Fix issues first, then re-verify.

Next Steps

MANDATORY IMPORTANT MUST ATTENTION — NO EXCEPTIONS after completing this skill, you MUST ATTENTION use

AskUserQuestion

to present these options. Do NOT skip because the task seems "simple" or "obvious" — the user decides:

"/cook (Recommended)" — Begin implementing feature stories on top of the scaffolding
"/workflow-review-changes" — Review scaffolding code before proceeding
"Skip, continue manually" — user decides

Closing Reminders

MANDATORY IMPORTANT MUST ATTENTION break work into small todo tasks using

TaskCreate

BEFORE starting. MANDATORY IMPORTANT MUST ATTENTION validate decisions with user via

AskUserQuestion

— never auto-decide. MANDATORY IMPORTANT MUST ATTENTION add a final review todo task to verify work quality. MANDATORY IMPORTANT MUST ATTENTION READ the following files before starting:

IMPORTANT MUST ATTENTION search 3+ existing patterns and read code BEFORE any modification. Run graph trace when graph.db exists.
IMPORTANT MUST ATTENTION verify all 4 production readiness foundations (quality tooling, error handling, loading state, Docker) before marking scaffold complete.
MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.
MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.