Claude Skills by kyle-chalmers

Check an app's numbers against the live warehouse — trace every Snowflake object it queries, verify the columns it expects actually exist, and map upstream lineage, using bounded read-only queries. Use when the user says "trace the data", "audit the lineage", "are these numbers right", "lineage for <slug>", or when a review finding hinges on what the live data returns.

Turn a user's feedback on a live app into applied fixes — classify each point, update the spec where scope changes, and land one commit per item. Use when the user says "here's feedback on <app>", "users said the numbers look wrong", "the filter is confusing", "polish this dashboard", or pastes review notes/screenshots about an existing app.

Port an external Streamlit app into the repo in two reviewable steps — lift-and-shift into apps/<slug>/, then conform to repo conventions until validation passes. Use when the user says "migrate a streamlit app", "port this dashboard into the repo", "bring an external app in", or "modernize this dashboard".

Run an app locally against live Snowflake so the user can see it in the browser, wiring up secrets.toml first if missing. Use when the user says "preview my app", "run my app", "let me see it in the browser", or after /start-app scaffolds an app.

Review an app the way a senior reviewer would — parallel reviewers across SQL, data, UI, runtime, and docs — then optionally apply the fixes. Use when the user says "review this app", "audit my dashboard", "fix the findings", "auto-fix until clean", or after validation passes. Flags — --fix applies findings as atomic commits, --auto loops review→fix until clean, --sql writes the paste-and-runnable SQL companions.

Stage, commit, push, and open a PR for one app, gated on a passing validation, then watch CI to a terminal state. Use when the user says "ship it", "open a PR", "deploy <slug>", or after preview and review look good.

The front door — build a Streamlit-in-Snowflake app from idea to opened PR, or resume one mid-build. Owns the spec, scaffold, page-building, and ship phases, with human checkpoints between them. Start here for any new app, to document an existing one, to add a page, or to set up a machine or repo. Use when the user says "build an app", "new dashboard", "add a page", "spec this out", "set me up", or "pick up where we left off".

The pass/fail check that must be clean before an app ships — runs `streamsnow validate-app <slug>` (required files, manifest, schema refs, security, bind predicates, caching, sql-tokens, session fallback, page imports, path leaks, the §11 build-state contract, plus a warn-only sql_review freshness section) and explains how to fix anything that fails. Use when the user says "validate", "is this ready", "check my app", or before /ship-app.