Building appsBeginner · about 30 minFree · no signup
Set up Claude Code skills, planning and project context
Create one reusable skill, plan your next change and give Claude clear project instructions.
By Alan Brown · Works with Claude Code
Use these three habits to make a coding project easier to pick up and repeat.
- 1. Save a repeated workflow as a skill. A project skill lives at .claude/skills/<name>/SKILL.md and can be invoked with a slash command. Start with one task you already repeat, such as reviewing a component. Official guide: code.claude.com/docs/en/skills
- 2. Plan before implementing a substantial change. Start Claude Code with claude --permission-mode plan, or use Shift+Tab until Plan Mode is active. Review the proposed files, approach and tests before approving edits. Official workflow: code.claude.com/docs/en/common-workflows
- 3. Keep project context in CLAUDE.md: verified commands, conventions and architectural decisions. /init can help create a starting point. Review what it produces; these instructions guide behaviour but do not enforce permissions. Official guide: code.claude.com/docs/en/memory
- Start here: use the copyable prompt below to draft a project-specific plan, one skill and a CLAUDE.md patch.
Context & limitations
The resources linked here are the official starting points. The separate 100+ resource collection mentioned in the video is not included in this guide.
Do this yourself
INSPECT THE PROJECT
Read the existing project instructions, package scripts and relevant code. Preserve existing instructions and uncommitted work. Ask one focused question if a missing requirement blocks a useful result. Verify current Claude Code documentation before choosing file formats or commands.PLAN ONE CHANGE
Propose the smallest complete implementation of my next feature. Name affected files, dependencies, acceptance criteria and suitable tests. Explain uncertainties. Do not implement the application change until I approve the plan; tell me how to enter Plan Mode in my installed version.DRAFT ONE REUSABLE SKILL
Turn my repeated task into .claude/skills/<clear-task-name>/SKILL.md. Include valid name and description metadata, when to use it, required inputs, concrete output and a completion check. Keep it narrowly scoped. Give me an example slash invocation and two realistic inputs to test. Show the file contents first; do not install unrelated skill packs.DRAFT PROJECT INSTRUCTIONS
Propose a concise addition to CLAUDE.md using only conventions and commands you verified in this repository. Include the build/test commands, relevant architecture and rules that would otherwise need repeating. Keep secrets out, identify unknowns, and avoid duplicating an existing instruction file.DELIVER THE STARTER KIT
Return the proposed plan, the skill file, the CLAUDE.md patch and a short validation checklist. Distinguish files drafted from files actually saved. After I approve the changes, apply only this setup and check the skill on a representative task.A repeatable workflow and project-specific instructions reduce repeated setup and make changes easier to review.
Want to build this with a teacher?
Pathwise Academy runs small, hands-on AI classes in Singapore for ages 10–17 and adults.