Sir-chawakorn/sanook-cli - 4페이지

shell-script-robust

Writes and reviews production-grade Bash/POSIX shell scripts with safety rails — set -euo pipefail, quoting, trap cleanup, shellcheck-clean, idempotency, and clear error handling. Triggers when authoring or hardening a shell/automation script, fixing a…

원문 언어: 영어

style-responsive-tailwind

Builds mobile-first responsive layouts with Tailwind CSS v4 using a consistent design-token scale, breakpoints, dark mode, and Flexbox/Grid; used when styling or fixing responsive UI.

원문 언어: 영어

terraform-plan-review

Reviews Terraform/OpenTofu plans and modules with a safety-first, diagnose-first lens — blast radius of destroys/replaces, identity churn, drift, state risks, secret exposure — before any apply. Triggers when reviewing a terraform plan diff, authoring…

원문 언어: 영어

type-safety-strict

Enforces strict static typing in TypeScript and Python (and hardens Rust/Go signatures), removing any/escape hatches and modeling state with precise types when code is loosely typed or fails the type checker.

원문 언어: 영어

validate-data-quality

Defines and runs rule-based data-quality checks — completeness, uniqueness, freshness, range, referential integrity — using Great Expectations-style assertion frameworks.

원문 언어: 영어

wrangle-tabular-data

Cleans, transforms, joins, reshapes, and aggregates tabular data (CSV/Parquet/DataFrames) with pandas, handling missing values, type coercion, dedup, and time-series resampling.

원문 언어: 영어

write-adr

Sanook captures a significant technical decision as a structured Architecture Decision Record (Michael Nygard format) — context, decision, alternatives considered, consequences — written to docs/adr/ as numbered files with an index.

원문 언어: 영어

write-analytical-sql

Writes accurate, readable, dialect-correct analytical SQL — CTEs, window functions, aggregations, and joins — across Postgres, BigQuery, Snowflake, and Databricks.

원문 언어: 영어

write-data-viz

Produces data visualizations and dashboards as code — matplotlib/seaborn/plotly static and interactive charts, plus D3.js/HTML dashboards — picking chart types that fit the data.

원문 언어: 영어

write-plan

Converts an approved design/PRD/RFC into a concrete, batched implementation plan — ordered steps, files to touch, dependencies, checkpoints, and a verification step per phase — ready to execute or hand to subagents.

원문 언어: 영어

write-playwright-e2e

Designs and stabilizes Playwright end-to-end tests — Page Object Model, role/data-testid selectors, cross-browser, network mocking, visual regression; used when adding or de-flaking browser tests.

원문 언어: 영어

write-prd

Produces an opinionated, implementation-ready Product Requirements Document (PRD) via interactive discovery — evidence-first problem statement, measurable goals with counter-metrics, scoped requirements, and explicit prioritization.

원문 언어: 영어

write-rfc

Sanook drafts an engineering RFC / design doc / technical proposal for a non-trivial change — motivation, proposed design, alternatives, tradeoffs, rollout/migration, risks, and open questions — structured for team review and sign-off.

원문 언어: 영어

api-design-review

Designs and reviews HTTP/REST and RPC API surfaces — resource naming, verbs, status codes, pagination, versioning, idempotency, error envelopes, and backward compatibility. Use when creating a new endpoint or changing an existing API contract.

원문 언어: 영어

code-review

Reviews the current git diff (or a target PR/branch) for correctness bugs, logic errors, edge cases, and missing error handling, grouping findings by severity (Critical/Warning/Suggestion). Use after implementing a non-trivial change and before declaring it…

원문 언어: 영어

db-migration-safety

Reviews and writes database migrations for safety — lock contention, blocking DDL on large tables, data-loss/destructive operations, missing indexes, and rollback plans. Use before running any schema change against a real or production database.

원문 언어: 영어

debug-root-cause

Diagnoses a failing test, crash, exception, or wrong output by reproducing the failure, isolating the cause, and fixing at the root — never by suppressing the error or weakening assertions.

원문 언어: 영어

dependency-upgrade

Upgrades and audits project dependencies safely — reads changelogs/breaking changes, bumps versions, fixes resulting breakage, and verifies with tests/build. Use when updating packages, resolving version conflicts, or patching a vulnerable dependency.

원문 언어: 영어

deploy-release

Prepares and runs a safe deploy/release — pre-flight checks (tests/build green, env vars, migrations applied), versioning/tagging, rollout, and post-deploy smoke verification with a rollback path. Use when shipping a build to staging/production.

원문 언어: 영어

explore-codebase

Explores an unfamiliar codebase to map architecture, locate where a feature lives, and find reusable utilities before writing code — returning a concise summary of entrypoints, key modules, and conventions. Use when entering a new repo or before a change that…

원문 언어: 영어

git-commit-pr

Stages and writes a Conventional Commits message from the actual diff, then opens a pull request with a structured description (summary, changes, test plan) using the gh CLI. Use when changes are ready to commit and/or turn into a PR.

원문 언어: 영어

performance-profiling

Diagnoses and fixes runtime performance problems — finds hotspots via profiling/measurement, then fixes N+1 queries, unnecessary allocations, blocking IO, and algorithmic complexity, proving the gain with before/after numbers. Use when something is measurably…

원문 언어: 태국어

refactor-cleanup

Improves changed code for reuse, simplification, readability, and efficiency without changing behavior, then re-runs tests to prove behavior is unchanged. Quality-only — it does NOT hunt for correctness bugs (use code-review for that).

원문 언어: 영어

security-review

Audits changed code for security vulnerabilities — injection (SQL/command/XSS), auth/access-control gaps, secrets in code, unsafe deserialization, SSRF, and insecure dependencies — reporting by severity with concrete remediation. Use when changes touch auth,…

원문 언어: 영어

write-docs

Generates and updates project-facing documentation from the actual codebase — README, API reference, usage examples, and changelog entries — staying in sync with real code, signatures, and config. Use when docs are missing, stale, or after a feature/API…

원문 언어: 영어

write-tests

Writes new automated tests for a function, API, parser, or module using a real test runner — TDD-first when the contract is clear (write test, run to FAIL, then implement). Use when adding test coverage or building a feature with a defined contract. Does NOT…

원문 언어: 영어