菜单
Studies existing code patterns, architecture, and conventions in react-gts-app. Reads reference components and tests to extract naming, import order, RTL query priority, and GTS-enforced conventions before writing new code. Use when writing new code, entering an unfamiliar area, or starting a session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Prepares a git commit for react-gts-app by analyzing staged changes and detecting commit style from the repo's signals — user history, recent repo history, commit templates, and any commit-msg hook. Confirms with the user only when signals conflict. Use when the user wants to commit changes or asks to prepare a commit message.
Studies existing code patterns, architecture, and conventions in react-gts-app. Reads reference components and tests to extract naming, import order, RTL query priority, and GTS-enforced conventions before writing new code. Use when writing new code or entering an unfamiliar area.
Runs the appropriate linter and formatter for specified files in react-gts-app. Maps file extensions to GTS-backed tools (eslint, prettier) and reports remaining errors. Use when linting a specific file or directory, or after editing code before moving on.
Generates a production-ready AGENTS.md and complete .claude/ setup through guided codebase discovery and targeted interview. Detects the user's global setup, the project's filesystem, and installed tooling — then asks the user to confirm rather than assuming. Creates skills, hooks, settings, and symlinks tailored to the project. Use when setting up a new project for AI-assisted development or updating an existing setup.
Implements a new feature in react-gts-app using a dialogue-first workflow: researches the codebase, asks one clarifying question at a time, explores 2–3 approaches with trade-offs, validates the chosen design section-by-section, then implements after approval. Use when implementing new functionality or a significant change.
Guides collaborative dialogue to turn ideas into designs through one-at-a-time questions, approach exploration with trade-offs, and incremental validation. Does not implement code. Use before creative work or significant changes — when the user asks to "brainstorm", "think through", "explore options for", or similar.
基于 SOC 职业分类
| name | learn |
| description | Studies existing code patterns, architecture, and conventions in react-gts-app. Reads reference components and tests to extract naming, import order, RTL query priority, and GTS-enforced conventions before writing new code. Use when writing new code, entering an unfamiliar area, or starting a session. |
| user-invocable | true |
| disable-model-invocation | false |
| argument-hint | [optional: area or pattern to study] |
Study existing code in example/src/ before writing anything new. GTS enforces formatting and most style rules automatically, so focus on the conventions GTS does not catch.
If $ARGUMENTS is provided, focus on that area or pattern. Otherwise, study example/src/ — it is the only source directory.
ls -lt example/src/*.tsx example/src/*.ts | head -5
Prefer recent, well-structured files. App.tsx, App.test.tsx, reportWebVitals.ts, and reportWebVitals.test.ts are good reference points.
Extract:
PascalCase.tsx for components, co-located PascalCase.test.tsx, co-located PascalCase.css.getByRole > getByText > getByTestId. @testing-library/jest-dom matchers.any; prefer unknown or generics. GTS forbids loose types.grep -rn "^export " example/src/ | head -20
Note exports available for reuse before inventing new ones.
Report:
file:line references.AGENTS.md § Anti-patterns)..claude/hooks/learn-on-start.sh. That adds tokens per session — flip disable-model-invocation: true in frontmatter if cost matters more than orientation speed.