Use this skill when the user wants to design or set up a hard quality gate for a TypeScript frontend repository or frontend subpackage. The scope is limited to web frontend and does not cover mobile clients or Python backend services.
Required reading
Before proposing changes, read these files in full:
../references/three-layer-model.md../references/landing-safety.md../references/github-review-and-rulesets.md../references/invocation-examples.md../references/gate-levels-and-template.mdreferences/platform-quality-gates.mdreferences/concrete-rules.md
These paths are all anchored to the directory containing this skill's SKILL.md ; after loading the skill, progressively read the corresponding materials by relative path.
Process
- Inspect the target repository's
AGENTS.md, package management files,package.jsonscripts, TypeScript configuration, lint and formatting configuration, test configuration, browser test setup, GitHub workflows, hook scripts, and existing gate orchestration entry points. - Form a plan according to the three-layer structure below.
- If rules need to be extended or the latest rule names need to be confirmed, first check
references/concrete-rules.md's official documentation entry points; do not add rules from memory alone. - Use
../references/gate-levels-and-template.md's tier table to give recommended tiers and trade-offs; do not decide the tier for the user. - Stop at the confirmation-before-write gate. Show the exact files planned to be created or modified and the remote settings, then request explicit user approval.
- After approval, implement the narrowest but useful scaffolding, run the new local entry point, and report the GitHub settings that still require manual handling.
Layer 1: Check tools
Identify executable TypeScript frontend checks: lint, typecheck, format check, unit tests, component tests, browser tests, build in package management scripts, as well as custom tests that protect lint or bundler configuration.
Layer 2: Check rules
Map each tool to the rules it enforces: formatting, lint policy, strict types, configuration drift, shared interface behavior tests, environment variable shape, build correctness, or browser flow coverage.
Layer 3: Invocation timing
Decide where checks run: local hooks provide fast feedback, pull request workflows serve as the authority, required status checks block merges, optional browser workflows cover critical user flows, and GitHub rulesets constrain review requirements.
Output form
Return a concise scaffolding plan including:
- files planned to be created or modified;
- Layer 1 tool table;
- Layer 2 rule table;
- Layer 3 invocation timing table;
- confirmation-before-write prompt;
- verification commands after implementation.