How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/blockmatic/basilic-skills --skill w-buildBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Use an existing plan or a sufficiently clear implementation request. Read repository instructions, affected README/scripts, matching rules and skills, and technical docs. Resolve consequential decisions from matching docs; ask a human for product scope, secrets, or destructive operations. Do not commit.
- Inspect the working tree and identify the files owned by this task. State the acceptance conditions; preserve unrelated changes. If there is no plan and the area spans packages or is unfamiliar, follow council steps 1–3 first.
- Implement one complete slice using existing packages and patterns. Change owning schemas and run documented generators instead of editing generated clients or migrations.
- Run the smallest existing check for this change. A reproducible logic defect should have a regression check; use TDD when requested or required by the repository, not as a ritual for prose edits. Never the full pre-push suite (
/w-shipowns that). - Investigate failed checks before building dependent work. Separate regressions caused here from pre-existing or environmental failures; never weaken checks to obtain a pass.
- If behavior, commands, or conventions changed, update matching MDX and nearest README; otherwise one line why not.
