Skeleton First Code SKILL
Description
AI coding agent workflow skill: long-context memory, anti-amnesia pipeline (Plan→Implement→Test), module tree + black box splitting, append-only planning/dev logs. Claude Code & OpenCode compatible. 面向 AI Agent 的骨架-血肉模块树开发方法论
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
README
Skeleton-First Code
**A workflow contract that makes AI coding agents build large projects the way software should be built: one module, one stage, one timestamped log entry at a time.**

**[🇬🇧 English](./README.md)** · **[🇨🇳 简体中文](./README_CN.md)**
The problem: why agents fail at big projects
Give a capable LLM agent a real project and, once the context grows long, it fails in three predictable ways:
| # | Failure | What it looks like |
|---|---|---|
| 1 | Long-context amnesia | Context compaction silently deletes the plan and early decisions. The agent resumes "from vibes": re-implements finished modules, contradicts settled choices, quietly drops goals it can no longer see. |
| 2 | Blind development | Writes the whole project as one impulse — code before architecture, features before tests. Declares "done" after a single green test tool. Fixes five modules at once and breaks them all. Plans 20 modules on day one, implements zero. |
| 3 | Unmaintainable output | A week later nobody (including the same agent) can answer: why does this exist, who touches what, what changed and when? Monolith files, god modules, no decision trail, no resume point. A project that cannot be resumed cannot be maintained. |
The root cause is structural, not intelligence: **an agent's context is volatile memory, but software development needs persistent memory and a scheduling discipline.**
The fix: Skeleton-First Code
This repository is a **SKILL.md workflow contract** (Claude Code / OpenCode / any agent that loads markdown instructions) that turns every code-writing task into a state machine the agent can never silently exit:
**Three pillars**
- Persistent Memory — every decision lives on disk: a README specification,
plans/planning logs,logs/development logs.
Related Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing