From coding-agent
Generates minimal project documentation — README.md, ARCHITECTURE.md with Mermaid diagrams, and AGENTS.md. Run after first feature ships or when docs are missing. Reads the actual codebase to generate accurate docs, not boilerplate.
npx claudepluginhub devjarus/coding-agentThis skill uses the workspace's default tool permissions.
Creates minimal, accurate project docs by reading the actual codebase. Not boilerplate — every line comes from what's really there.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Creates minimal, accurate project docs by reading the actual codebase. Not boilerplate — every line comes from what's really there.
Claude Code reads CLAUDE.md at session startup. Most OSS projects use AGENTS.md as the canonical agent workflow document (stack, build/test commands, conventions, known issues). Do not duplicate content between them — duplication guarantees drift.
The rule: one file is the source of truth, the other is a pointer. In practice, AGENTS.md holds the content and CLAUDE.md is a 5-line redirect:
# Project Notes
This project uses [AGENTS.md](./AGENTS.md) as the canonical agent workflow document.
See AGENTS.md for: stack, build/test commands, conventions, architecture decisions, and known issues.
If this project was created before AGENTS.md became standard and already has a detailed CLAUDE.md, invert the relationship: keep CLAUDE.md as the source of truth and make AGENTS.md the redirect. Never maintain both.
# Project Name
[1-sentence description from spec.md or package.json]
## Quick Start
[exact install + run commands — read from package.json scripts, Makefile, etc.]
## Tech Stack
[language, framework, database, key deps — from package.json/go.mod/Package.swift/requirements.txt]
## Project Structure
[tree of key directories with 1-line descriptions — from actual file scan]
## Testing
[exact test commands + what they cover]
## API Reference (if applicable)
[endpoints with methods, paths, request/response shapes — from route files]
## License
[from LICENSE file if exists]
Use ASCII diagrams — they render everywhere with no dependencies. Read the actual code to generate these.
# Architecture
## Overview
[2-3 sentences: what the system does, key design decisions]
## System Diagram
[ASCII box diagram showing major components and connections]
## Data Flow
[ASCII flow showing a primary user flow end-to-end]
## Data Model
[ASCII table showing schema — fields, types, relationships]
## Key Components
[for each major module: what it does, what it depends on, key files]
## Technical Decisions
[from spec.md Technical Risks / Architecture Decisions if available, otherwise infer from code]
# Development Workflow
## Stack
[language, framework, database, key libraries with versions]
## Build & Run
[exact commands]
## Test
[exact commands — unit, integration, e2e]
## Project Structure
[key directories]
## Conventions
[patterns, naming, file organization]
## Architecture Decisions
[key decisions and why]
## Known Issues
[from review.md findings if available]
## Development Notes
[gotchas, ordering requirements, env setup]
Read these files to understand what exists:
package.json / go.mod / Package.swift / requirements.txt → stack + depsspec.md, plan.md (if in .coding-agent/) → requirements + architecture decisionssrc/index.*, src/app.*, main.*) → how the app startsUse plain ASCII art. Examples:
System diagram:
┌──────────────┐ HTTP ┌──────────────┐ SQL ┌──────────┐
│ React Client │───────────→│ Express API │──────────→│ SQLite │
│ :5173 │←───────────│ :3001 │←──────────│ │
└──────────────┘ └──────────────┘ └──────────┘
Data flow:
User → Frontend → POST /api/posts → Validate → INSERT INTO posts → Return 201 → Redirect to /posts/:slug
Data model:
posts
├── id INTEGER PK autoincrement
├── title TEXT NOT NULL
├── slug TEXT UNIQUE
├── content TEXT NOT NULL
├── excerpt TEXT
├── tags TEXT
├── createdAt TEXT
└── updatedAt TEXT
Write each file at the project root. Keep them minimal:
express@4.21.0, write that — not just "Express".