Menu
O SkillsMP coletou 8 skills de shiguri-01/preview-pdf. Abra uma skill para revisar a origem e os detalhes.
Mostrando 8 de 8 skills coletadas.
Edit or review pvf developer docs under docs/. Use when changing docs/ files, trimming or migrating stale docs, deciding whether information belongs in docs, code comments, or tests, or checking architecture/reference/testing doc ownership and drift risk.
Idioma do texto original: inglês
Add, update, place, or review pvf tests and validation. Use when writing regression tests, protecting behavior changes, choosing unit/module/integration test boundaries, reviewing test quality, changing test policy, or deciding validation commands.
Idioma do texto original: inglês
Add, edit, rename, or review pvf palette behavior. Use when changing PaletteKind, PaletteProvider implementations, palette open options, provider snapshots, candidate rows, command-palette visibility, input modes, selection behavior, tab or submit behavior,…
Idioma do texto original: inglês
Add, edit, rename, or review pvf command behavior. Use when changing command ids, arguments, parsing, roles, exposure, invocation policy, target requirements, enabled_when runtime conditions, command palette visibility, key bindings, help text, or command…
Idioma do texto original: inglês
Run and interpret pvf headless performance diagnostics. Use for generating benchmark PDF fixtures, running `cargo bench --bench perf`, writing JSON reports, comparing results across PDFs or code changes, and explaining scenario metrics or regressions.
Idioma do texto original: inglês
Add, edit, rename, or review pvf extension behavior. Use when changing Extension implementations, ExtensionHost composition, extension-owned state, input hooks, AppEvent handling, background drain, status bar segments, extension UI snapshots, or reload/reset…
Idioma do texto original: inglês
Create and review GitHub pull requests with a consistent workflow. Use this whenever the user asks to create a PR, open/view PR details, draft PR text, or prepare changes for merge.
Idioma do texto original: inglês
Locate Rust crate source and documentation paths by asking Cargo instead of assuming ~/.cargo. Use when the user asks to inspect a crate implementation, find local crate files, or get the matching docs.rs URL for a dependency.
Idioma do texto original: inglês