From the plan to the first step
Turn the plan into
your first build steps.
Your kit is a set of project-specific Markdown documents. Read them before giving them to an AI coding tool or developer. They explain the recommended approach, important decisions, build milestones and checks, with guidance for maintaining and evolving the result where relevant.
Download and unzip the pack.
Open your project and select Download ZIP. Extract it and keep the project-kit folder together so references between files still make sense. A normal text editor can open Markdown (.md) files.
Open START-HERE.md.
It points to the project summary, open decisions, setup guidance and build steps. FILE-MAP.md helps you find the document for each task.
Check the agreed scope.
Read docs/01-PRODUCT-SCOPE.md and docs/08-OPEN-DECISIONS.md. Check that features and permissions match your intention. Resolve a decision that blocks the next step before asking a builder to assume an answer.
Choose your builder or developer.
Working with an AI coding tool
Open your project in your preferred tool. Find its starting instructions in prompts/. Supply the referenced files manually, using the tool’s file attachment or project-context feature where available. If it cannot read local files, paste the relevant text. Check that the tool has read the files before asking it to act.
Working with a developer
Share the ZIP with the person implementing your project. Ask them to review scope, access rules, open decisions and the suggested setup, then review any existing implementation and propose the next useful milestone with an observable check.
Choose the next useful step.
Use the supplied prompt with the relevant files. For a new project, begin with the first milestone. If work already exists, ask the builder to inspect it and identify what is complete before proposing changes. Agree on the next step and its checks before starting. The kit is guidance; it does not automatically import into a tool or deliver a finished application.
A useful first prompt
Read START-HERE.md and the relevant project documents. Inspect existing code or workflow configuration if you can access it; otherwise say what you cannot inspect. Summarise the goal, existing progress and important decisions. Do not edit files yet. Propose the next small implementation step and the checks that will confirm its outcome.
Run the checks in the plan.
Review each change and its checks before continuing. Ask the builder to explain failures plainly. AI can make mistakes; a confident answer does not replace testing the build.
Keep the plan current.
If a major requirement changes, update your project in PenguinKit and use an included kit update before continuing from an outdated plan. Keep earlier downloads for comparison.
Do not paste passwords, private keys or real customer information into a coding tool unless you have checked how it handles the information.