Loading...
Loading...
Found 177 Skills
Use when working with TypeScript projects, tooling, and ecosystem. Covers the type system, project configuration, package management, CLI development, and library packages. USE FOR: TypeScript language features, choosing build tools, package managers, project structure, type system guidance, runtime selection DO NOT USE FOR: specific tool configuration details (use the sub-skills: project-system, package-management, cli, packages)
Write Python code following best practices. Use when developing Python applications. Covers type hints, async, and modern tooling.
Extract, compare, and propagate tooling improvements across FVH repos. Use when user says "sync workflows", "propagate config", "diff workflows", "extract improvements", or "config sync".
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
Configure TypeScript project tooling for existing Node or frontend projects without app scaffolding. Use for TS starter setup, TS lint/format/test setup, Node TypeScript starter, or Vite TypeScript config requests.
TypeScript/JavaScript project workflow guidelines using Bun package manager. Triggers on `.ts`, `.tsx`, `bun`, `package.json`, TypeScript. Covers bun run, bun install, bun add, tsconfig.json patterns, ESM/CommonJS modules, type safety, Biome formatting, naming conventions (PascalCase, camelCase, UPPER_SNAKE_CASE), project structure, error handling, environment variables, async patterns, and code quality tools. Activate when working with TypeScript files (.ts, .tsx), JavaScript files (.js, .jsx), Bun projects, tsconfig.json, package.json, bun.lock, or Bun-specific tooling.
Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.
Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.
Keep AI tooling files (.claude, .codex, .cursor, .windsurf, .augment, .kiro, .cline, .roo, .gemini, etc.) on dev branch but exclude them from main/master. Use when managing branches, creating PRs to main, merging to main, or setting up a repo's branch strategy for AI-assisted development. Triggers on git merge/PR operations targeting main or master.
Routes to Chainalysis public Sanctions Screening surfaces—the free Sanctions REST API (address checks against OFAC SDN crypto listings) and the EVM on-chain oracle—plus how they differ from paid Chainalysis customer data. Use when the user references Chainalysis sanctions tooling, public.chainalysis.com, or repo notes in Chainalysis.md—not for legal conclusions, full vendor ToU reproduction, or substituting official government sanctions lists.
Generate polished technical diagrams as SVG, and export PNG when local export tooling is available. Use when the user wants an architecture diagram, flowchart, data flow, sequence diagram, agent or memory diagram, comparison matrix, timeline, or concept map rendered as a visual artifact instead of Mermaid or a hand-drawn whiteboard. Trigger on requests like 画图、帮我画、生成图、 做个图、架构图、流程图、时序图、可视化一下, or English requests such as draw diagram, architecture diagram, visualize this system, generate a flowchart, or create a technical SVG. Prefer this skill when the user wants publishable SVG/PNG output, style selection, or AI/agent-system diagram conventions.
MUST be used whenever fixing test coverage for a Dune app to meet the 80% line coverage hard gate. This skill finds AND fixes coverage gaps — it configures tooling, writes missing tests, covers untested paths, and refactors code for testability. It does not just report. Triggers: test coverage, fix tests, write tests, add tests, coverage fix, 80% coverage, coverage gate, missing tests, testability, vitest coverage, jest coverage.