Automated summary
Runs the complete validation suite for Topographic Studio projects, including linting, type checking, testing, and building.
Strengths
- Automates all quality checks in a single command.
- Stops on first failure for quick feedback.
- Provides detailed error reports with fix suggestions.
Limitations
- Specific to projects using Biome, TypeScript, Bun, and a monorepo structure.
- Does not cover integration or end-to-end tests.
Before every commit, pull request, or package publish to ensure code quality.
For quick partial checks (e.g., only tests) or in projects that don't use the expected tech stack.
Security analysis
SafeThe skill runs standard development commands (bun run lint/typecheck/test/build) sequentially, with no destructive or exfiltrating actions. No obfuscation, no disabling of safety, and no use of dangerous utilities like curl or shell redirections to secrets.
No concerns found
How this analysis is madeExamples
Run the full validation suite for Topographic Studio.I'm about to push a PR. Please run all checks (lint, typecheck, test, build) and report any failures.We're releasing a new version. Execute the complete validation suite and show a summary.Check All Skill
Run the complete validation suite for Topographic Studio projects.
Task
You are helping the user validate their code with a full quality check suite.
Instructions
Run these checks in order:
-
Lint - Check code style with Biome
bun run lint -
Type Check - Verify TypeScript types
bun run typecheck -
Test - Run all tests
bun run test -
Build - Build all packages
bun run build
Execution Strategy
- Run checks sequentially
- Stop on first failure (report error immediately)
- If all pass, show comprehensive success summary
Error Reporting
For each failed check, provide:
- Which check failed (lint, typecheck, test, or build)
- Specific error messages
- File locations where errors occurred
- Suggestions to fix
Success Criteria
All checks must pass:
- ✅ No linting errors
- ✅ No type errors
- ✅ All tests passing
- ✅ All packages build successfully
Output Format
Running full validation suite...
[1/4] Linting with Biome... ✅
[2/4] Type checking... ✅
[3/4] Running tests... ✅
[4/4] Building packages... ✅
✨ All checks passed! Ready for commit/release.
Summary:
- Linted: 127 files, 0 errors
- Type checked: 45 files, 0 errors
- Tests: 23 passed
- Built: 4 packages
When to Use
- Before committing changes
- Before creating a pull request
- Before publishing packages
- As part of CI/CD validation
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/complete-project-validation-mm5t8bln/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/complete-project-validation-mm5t8bln' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/complete-project-validation-mm5t8bln/download' --output '.skill-downloads/complete-project-validation-mm5t8bln/SKILL.md.part' && mv '.skill-downloads/complete-project-validation-mm5t8bln/SKILL.md.part' '.skill-downloads/complete-project-validation-mm5t8bln/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/complete-project-validation-mm5t8bln/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.