idaibin
UserIndependent Agent Skills for repository analysis, planning, implementation, review, delivery, design, and runtime verification.
Categories
Indexed Skills (13)
ui-spec
Use when a selected visual source or accepted UI surface must become an implementation-ready Feature Spec or a Google DESIGN.md shared visual contract covering layout, states, interaction, responsive/accessibility behavior, components, tokens, and acceptance; do not use for visual exploration, image generation, or frontend source edits.
ask-chatgpt
Use when the user requests a local ChatGPT request package or explicitly authorizes an independent ChatGPT review, research result, visual exploration, or decision challenge; do not use when Codex or an available host tool can complete the result directly.
dev-frontend
Use when a frontend change must be implemented or refactored across UI, state, data, styling, build/tooling, accessibility, performance, or desktop integration; owns source edits and validation, not audit-only, browser-only, UI-spec, or Git-delivery work.
dev-rust
Use when a Rust source change must be implemented, ported, or refactored across APIs, crates, services, CLIs, async, persistence, unsafe or FFI boundaries, tests, or docs; owns source edits and validation, not audit-only, review-only, or Git-delivery work.
domain-modeling
Use when shared business terms, meanings, rules, lifecycle conflicts, or domain boundaries are ambiguous across product work and must be resolved before specification or implementation; route feature-local behavior and acceptance to product-spec.
human-writing
Use when drafting, rewriting, proofreading, diagnosing, or adapting source-grounded prose, especially technical articles, essays, tutorials, product notes, and social posts, while preserving facts, attribution, uncertainty, voice, and meaning. Supports private English-first reasoning for Chinese finals; not translation-only, fiction, or AI-detection evasion.
ops-browser
Use when directly operating or verifying a specified page, or gathering evidence for an isolated browser-layer failure; require an available browser, verified target, and proven capability, not ChatGPT orchestration, desktop-client proof, or cross-system diagnosis.
ops-client
Use when directly operating or verifying a specified real desktop client, or gathering evidence for an isolated client-layer failure; require a verified target, window, and capability, not browser-page verification, source changes, or cross-system diagnosis.
product-spec
Use when an ambiguous product feature, new product boundary, or named product fact source must become the smallest implementation-ready specification; owns product decisions and authorized spec artifacts, not selected-source UI specification or implementation.
repo-delivery
Use when reviewed changes need authorized Git mutation: categorized commits, push or sync, branch integration, temporary-branch cleanup, or ref proof; owns Git delivery and stops before pull-request creation.
repo-map
Use when current Git or non-Git workspace truth needs a durable map of roots, ownership, architecture, commands, task routes, and reusable contracts, or an existing map needs evidence-based repair; do not use for ordinary task-local discovery or change review.
repo-review
Use when current Worktree changes or a fixed snapshot/range, including a resolved pull request, need coordinated read-only Standards and Spec findings; use audit-* for a bounded domain audit with no change basis.
ui-design
Use when a concrete page or flow needs evidence-grounded visual and interaction design before frontend implementation, or shared tokens, component semantics, variants, or the product-wide visual system must change.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.