From app-dev
This skill should be used before claiming any work is complete, before committing, before creating PRs, or before reporting task status. Enforces fresh verification evidence for all completion claims. Provides the verification gate methodology: run commands, read output, then report.
npx claudepluginhub iwritec0de/claude-plugin-marketplace --plugin app-devThis skill uses the workspace's default tool permissions.
**Evidence before claims, always. NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION.**
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Evidence before claims, always. NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. If you have not run the verification command in the current session, you cannot claim it passes. Prior knowledge, assumptions, and memory of previous runs do not count. Only fresh output from the current session constitutes evidence.
Every completion claim must pass through this gate:
Before claiming work is complete in this project, run each applicable command and confirm clean output:
| Check | Command | What it proves |
|---|---|---|
| Type checking | tsc --noEmit | No type errors across the project |
| Tests | npx vitest run or npm test | All tests pass |
| Lint | npx eslint . | No lint errors or warnings |
| Formatting | npx prettier --check . | All files match formatting rules |
| Production build | next build | Build succeeds, catches SSR/hydration issues |
Run these in order. A type error caught by tsc is cheaper to fix than one discovered during next build. A lint error is cheaper to fix before tests run.
If a project uses a different test runner, linter, or build tool, substitute the appropriate commands. The principle is the same: run the real tool, read the real output.
These phrases are signals that the verification gate has NOT been passed:
If you catch yourself using these phrases, stop and run the actual command.