Files

23 lines
1.3 KiB
Markdown

# AI-Assisted Development: How Ironpad Was Built
Ironpad was built entirely using AI-assisted development. Not just the code -- the architecture, the PRD, the task breakdowns, and the debugging were all done through structured collaboration with AI models.
We share this process openly as part of the **Open Method** philosophy: not just open source code, but open development process.
## What's in This Folder
| Document | Description |
|----------|-------------|
| [method.md](method.md) | The complete AI development workflow: PRD-first, task decomposition, handover system |
| [tools.md](tools.md) | Every tool used, how it fits in, and why |
| [lessons-learned.md](lessons-learned.md) | What worked, what didn't, and the 200K to 1M context window shift |
## Articles
- [The AI Development Workflow I Actually Use](https://dev.to/olaproeis/the-ai-development-workflow-i-actually-use-549i) -- The original workflow article describing the method
- [From 200K to 1M: How Claude Opus 4.6 Changed My AI Development Workflow](docs/article-opus-4.6-workflow.md) -- Follow-up on the context window leap
## Key Takeaway
The tools keep getting better, but **the process of using them well still matters**. A 1 million token context window doesn't help if you don't know what to ask for. Structure your work, be specific, maintain context, verify results.