kongyo2
- 15 skills
- 0 followers
- 10 hours ago last updated
- ▌ Tdd · kongyo2 bundleStrict t-wada style Red-Green-Refactor TDD for TypeScript + Vitest projects. Use when implementing features, fixing bugs, changing runtime behavior, or refactoring logic — any task that adds or modifies production code. Enforces test-first development with a verified Red, minimal Green, and disciplined Refactor, plus agent-safe Vitest execution rules.
- ▌ Aistudio Spec Builder · kongyo2 bundleCreates high-quality specification documents for Google AI Studio's app builder. This skill should be used when users want to create or refine specifications for React + TypeScript web applications that will be built using Google AI Studio's Build feature. The skill guides users through requirements gathering, functional decomposition, UI/UX design, and produces structured specifications without any code, using only natural language instructions.
- ▌ Deep Research · kongyo2 bundleThis skill should be used when the user requests comprehensive research, deep investigation, or detailed academic-style reports on any topic. Trigger phrases include "deep research", "comprehensive investigation", "detailed report", "academic research", or requests for thorough analysis of complex subjects. The skill produces multi-thousand word reports in markdown format with extensive citations.
- ▌ Kongyo TS Prettier Setup · kongyo2Set up Prettier code formatter for TypeScript npm projects with merge-safe defaults.
- ▌ Kongyo TS React Doctor · kongyo2TypeScript React プロジェクトで react-doctor を使うときに使う。React の変更後、レビュー前、バグ修正後、品質確認時に適用する。最初の行動は必ず `npx -y react-doctor@latest . --verbose` をリポジトリルートで実行すること。診断結果は参考情報として扱い、不完全な実行を明示し、修正はローカルのコード文脈に照らして必要なものだけ行う。
- ▌ Markdown Skill Creator · kongyo2 bundleGuide for creating effective markdown-only Claude Skills that function without executable scripts. Use when creating skills based on knowledge, guidelines, templates, workflows, or domain expertise. Covers structure, patterns, best practices, and provides templates for common skill types (guidelines, workflows, template collections, domain knowledge, principles-based guidance).
- ▌ Stellaris Modding · kongyo2 bundleUse when creating, editing, or reviewing Stellaris mods and you need self-contained guidance on Clausewitz/PDX script structure, file placement, scopes, triggers, effects, on_actions, events, technologies, buildings, districts, POP/jobs, traits, governments, relics, archaeology, decisions, special projects, situations, megastructures, components, zones, or vanilla-aligned conventions informed by CWTools and vanilla Stellaris.
- ▌ TS Comment Purge · kongyo2Unconditionally strip every line and block comment from a TypeScript codebase with npx @kongyo2/ts-comment-scanner - AST-based, so strings, template literals, regexes, and JSX text are never touched, and compiler/linter directives (@ts-expect-error, eslint-disable, oxlint-disable, prettier-ignore, ...) plus license headers are preserved automatically. Use whenever comments should be removed, stripped, or cleaned from TS/TSX code - purging AI-generated noise comments after an agent session (--diff scopes to changed files), enforcing a no-comment policy, or any "remove the comments" request, even when the user doesn't name the tool. Also covers scanning and inventorying comments (text/JSON/GitHub-annotation output) without removing them.
- ▌ Agent Primary TS Starter · kongyo2 bundleBootstrap or harden a TypeScript npm project the agent-primary way - tsconfig.json (TypeScript 7, maximally strict, machine-verifiable), Prettier (diff- and line-number-stable formatting), and Oxlint (bug-focused linting with machine-readable output), wired together with npm scripts and CI gates. Use whenever a TS npm project is being created, configured, or reviewed; whenever a tsconfig.json is created, edited, reviewed, troubleshot, or even just discussed - default to this skill instead of free-recall whenever the answer involves a tsconfig field; and whenever formatting or linting is being added or tuned - even if the user never says "tsconfig", "prettier", "oxlint", "formatter", or "linter".
- ▌ TS NPM Zod Starter · kongyo2Add zod to a TypeScript npm project and install the boundary-only parsing convention. Use when starting a new TS project that needs runtime schema validation, or when layering zod onto an existing TS npm project — even if the user doesn't explicitly say "zod" or "validation".
- ▌ TS NPM Oxlint Starter · kongyo2Add Oxlint to a TypeScript npm project with agent-friendly defaults that focus error-level diagnostics on real bugs, silence stylistic noise, and emit output in oxlint's `agent` format for downstream LLM consumption. Use when bootstrapping a new TS project that needs linting, or when adding Oxlint to an existing TS npm project — even if the user doesn't explicitly say "oxlint" or "linter".
- ▌ TS NPM Prettier Starter · kongyo2Add Prettier to a TypeScript npm project with agent-friendly defaults that minimize diff size and keep line numbers stable across LLM-driven edits. Use when bootstrapping a new TS project that needs auto-formatting, or when adding Prettier to an existing TS npm project — even if the user doesn't explicitly say "prettier" or "formatter".
- ▌ TS Tsconfig Modern Strict Starter · kongyo2Set up a TypeScript 7 tsconfig.json with maximally strict, machine-verifiable settings tuned so the LLM agent doing the editing gets the largest possible share of its mistakes reported as compiler errors, in output it can consume. Use whenever a tsconfig.json is being created, edited, reviewed, troubleshot, or even just discussed — apply the standing policy even when the user only asks about a single option. Default to this skill instead of free-recall whenever the answer involves a tsconfig field.
- ▌ Skill Alpha · kongyo2Alpha skill used by unit tests — exercises the happy path of frontmatter parsing and tokenization.
- ▌ Skill Bravo · kongyo2Bravo skill used by unit tests — provides a second entry so sorting and multi-skill ranking can be verified.