القائمة
Verify code quality after making changes in this project. Use this skill whenever you've finished implementing a feature, fix, or refactor and need to run the verification pipeline.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Use it to load and enforce domain glossary throughout the task.
Use when writing, editing, or restructuring a guide, reference page, or any content under the `docs/` directory.
Use this skill when adding, editing, or reorganizing translations in the main app.
Make changes to the UI Kit. Use this skill when you need to create new or update existing UI components, their themes, stories, or tests.
Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
| name | embroiderly-verify |
| description | Verify code quality after making changes in this project. Use this skill whenever you've finished implementing a feature, fix, or refactor and need to run the verification pipeline. |
After finishing code changes, run the verification pipeline to ensure quality. The goal is to catch issues early without doing more work than necessary.
Scoping principle: always target the narrowest set of packages/crates that covers the changes plus their dependents. When the scope is broad or uncertain, run the workspace-wide command.
| Package | Path |
|---|---|
@embroiderly/app | app/ |
@embroiderly/image-import | packages/image-import/ |
@embroiderly/pdf-export | packages/pdf-export/ |
@embroiderly/ui | packages/ui/ |
graph LR
app["@embroiderly/app"]
img["@embroiderly/image-import"]
pdf["@embroiderly/pdf-export"]
ui["@embroiderly/ui"]
img --> app
pdf --> app
ui --> app
| Crate | Path |
|---|---|
embroiderly | app/src-tauri/ |
embroiderly_editor | crates/embroiderly-editor/ |
embroiderly_image | crates/embroiderly-image/ |
embroiderly_parsers | crates/embroiderly-parsers/ |
embroiderly_pattern | crates/embroiderly-pattern/ |
embroiderly_tracing | crates/embroiderly-tracing/ |
embroiderly_web | crates/embroiderly-web/ |
Each Wasm module lives in a src-wasm/ subdirectory and exposes autogenerated TypeScript bindings via its pkg/ directory.
| Module | Path | Consumed by |
|---|---|---|
embroiderly_wasm | app/src-wasm/ | @embroiderly/app |
embroiderly_image_import | packages/image-import/src-wasm/ | @embroiderly/image-import |
embroiderly_pdf_export | packages/pdf-export/src-wasm/ | @embroiderly/pdf-export |
Type checking requires the autogenerated TypeScript bindings in each Wasm module's pkg/ directory.
Build only the Wasm modules whose Rust sources changed, using dev mode.
pnpm -F <package> wasm:build-dev # or `pnpm -r wasm:build-dev` to build all three Wasm module.
Skip this step if only TypeScript sources changed and all pkg/ directories already exist from a previous build.
pnpm [-F <package>] check-types
cargo check --locked [-p <crate>]
Frontend:
pnpm lint:fix
pnpm fmt:fix
Backend:
cargo clippy --locked --fix --allow-dirty -- -D warnings
cargo +nightly fmt
Run both if you changed both sides. This fixes trivial issues and reports non-fixable issues inline.
Frontend: app/ has separate test:unit (logic) and test:components (Vue components) scripts.
Run only what's relevant.
pnpm [-F <package>] test
Backend:
cargo nextest run --locked --no-fail-fast [-p <crate>]