My favorite tools

My current development workflow

1. 01

   Everything starts in the terminal

   I start every new project from the terminal with Claude Code or OpenCode. I usually prefer OpenCode because the command-line experience feels more familiar and I like seeing token usage in real time. Sometimes I gather reference images first, then send a structured prompt in a new file asking for the project PLAN: approach, development style, and core features. That is where I make the first adjustments.

   Claude Code OpenCode PLAN
2. 02

   Exact technologies and versions

   I choose the technologies I want to use and check their current versions manually before adding them to the plan. I always request the latest pnpm release for the additional supply-chain safety provided by minimumReleaseAge.

   pnpm minimumReleaseAge
3. 03

   Best practices with Autoskills

   Once the plan is adjusted and the first iteration is moving, I use autoskills.sh to detect the project's technologies and apply focused best practices for each one.

   autoskills.sh ↗
4. 04

   Token optimization

   Before moving into more specific changes, I use the Ponytail plugin to reduce token usage and make the workflow more efficient.

   Ponytail
5. 05

   Documentation that stays alive

   I keep each project's README up to date, usually through a dedicated prompt, so the current state and decisions remain easy to understand.

   README
6. 06

   Learning while building

   I ask for explanations to be genuinely educational, like a personal class. I sometimes build with technologies I have not mastered yet and study them as I go, evolving the product and my own understanding at the same time.

   Continuous learning

$ an ever-evolving method — there is still plenty to improve, but this is how I build today.