init: scaffold Seth-Workflow-April-2026
User-agnostic, shareable AI-assisted development workflow distilled from 26+ real projects. Includes 9 composable rules, 4 project templates, pre-push secret scanning hook, 3 methodology guides, and customization docs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,54 @@
|
||||
# <Project Name>
|
||||
|
||||
> <One-line description of the project.>
|
||||
|
||||
## Start Here
|
||||
|
||||
1. Read this file for project state and architecture
|
||||
2. Check `.claude/sessions/` for the latest session handoff
|
||||
3. Read SESSION.md for accumulated decisions and discoveries
|
||||
|
||||
## Project State
|
||||
|
||||
- **Phase:** <IDEATION | PLANNING | BUILDING | REVIEW | SHIPPING>
|
||||
- **Branch:** <current active branch>
|
||||
- **Tests:** <number passing, or "none yet">
|
||||
- **Deployment:** <where it runs, or "local only">
|
||||
|
||||
## Architecture
|
||||
|
||||
<High-level description of how the system works. Key components and how they connect.>
|
||||
|
||||
### Key Files
|
||||
|
||||
| File | Role |
|
||||
|------|------|
|
||||
| <path> | <what it does> |
|
||||
|
||||
## Infrastructure
|
||||
|
||||
<Deployment target, services, ports, URLs.>
|
||||
See `CONTEXT.md` for detailed infrastructure facts.
|
||||
|
||||
## Conventions
|
||||
|
||||
- Conventional commits: `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`
|
||||
- <Any project-specific conventions>
|
||||
|
||||
## Credentials
|
||||
|
||||
All credentials are in `.env` (gitignored, never committed).
|
||||
**Never inline credentials in code, docs, or messages.**
|
||||
|
||||
## Development
|
||||
|
||||
```bash
|
||||
# Setup
|
||||
<setup commands>
|
||||
|
||||
# Run
|
||||
<run commands>
|
||||
|
||||
# Test
|
||||
<test commands>
|
||||
```
|
||||
@@ -0,0 +1,36 @@
|
||||
# CONTEXT.md -- Infrastructure & Deployment Context
|
||||
|
||||
> Static facts about where and how this project runs.
|
||||
> Update when infrastructure changes. Don't put session-specific notes here -- those go in SESSION.md.
|
||||
|
||||
## Deployment
|
||||
|
||||
| Property | Value |
|
||||
|----------|-------|
|
||||
| Host | <hostname or IP> |
|
||||
| Port | <port number> |
|
||||
| Service name | <systemd service, container name, etc.> |
|
||||
| URL | <public URL if applicable> |
|
||||
|
||||
## Dependencies
|
||||
|
||||
| Dependency | Version | Purpose |
|
||||
|------------|---------|---------|
|
||||
| <name> | <version> | <what it's used for> |
|
||||
|
||||
## Configuration
|
||||
|
||||
<Key configuration files and their locations. Environment variables needed.>
|
||||
|
||||
```
|
||||
# Required environment variables
|
||||
<VAR_NAME>=<description>
|
||||
```
|
||||
|
||||
## Architecture Notes
|
||||
|
||||
<How the system fits together. What talks to what. Key design decisions.>
|
||||
|
||||
## Known Issues
|
||||
|
||||
<Infrastructure-specific issues, workarounds, and gotchas that anyone working on this project needs to know.>
|
||||
@@ -0,0 +1,20 @@
|
||||
# IDEA.md -- Project Idea
|
||||
|
||||
> This is the starting point an AI agent reads before any code exists.
|
||||
> Keep it honest and rough -- it does not need to be polished.
|
||||
|
||||
## What is this?
|
||||
|
||||
<Describe the project in plain language. What does it do? Who is it for?>
|
||||
|
||||
## Problem it solves
|
||||
|
||||
<What pain point or gap does this address? Why does it need to exist?>
|
||||
|
||||
## Constraints / preferences
|
||||
|
||||
<Language, stack, deployment target, performance requirements, anything relevant.>
|
||||
|
||||
## Success criteria
|
||||
|
||||
<How do you know this is done? What does "working" look like?>
|
||||
@@ -0,0 +1,38 @@
|
||||
# SESSION.md -- Persistent AI Session Memory
|
||||
|
||||
## What this file is for
|
||||
|
||||
This is a **persistent memory file** -- it accumulates decisions, discoveries, and context across AI coding sessions so the assistant doesn't start cold each time.
|
||||
|
||||
It is **not** a chat transcript.
|
||||
It is **not** static documentation of how something works.
|
||||
It is a living record of *why things are the way they are*, plus a map to the right context files.
|
||||
|
||||
---
|
||||
|
||||
## Project Summary
|
||||
|
||||
<One paragraph: What is this project? What problem does it solve?>
|
||||
|
||||
## Context Files
|
||||
|
||||
- `./CLAUDE.md` -- project instructions and architecture
|
||||
- `./CONTEXT.md` -- infrastructure and deployment details
|
||||
- `./README.md` -- project overview
|
||||
|
||||
## Session Notes
|
||||
|
||||
Group entries by topic, not by date. Update the relevant section rather than appending raw timestamped blocks.
|
||||
|
||||
### Infrastructure decisions
|
||||
|
||||
<Decisions about hosting, deployment, dependencies, architecture.>
|
||||
|
||||
### Bug fixes & discoveries
|
||||
|
||||
<Problems found and how they were resolved. Include the "why" so the fix makes sense later.>
|
||||
|
||||
### Open threads
|
||||
|
||||
- [ ] <Things that need to be done but haven't been started yet>
|
||||
- [ ] <Known issues that aren't blocking but should be addressed>
|
||||
Reference in New Issue
Block a user