Coding & Development

GitHubのissueを起票するときの書き方（タスク用・不具合用のテンプレート、タイトル、ラベル、依存関係の書き方）。「issueを作って」「issueに起こして」「これをissueにしておいて」「バグ報告を書いて」「タスクを分割してissueにして」など、GitHubにissueを新規作成する・issue本文を下書きするときは必ず使うこと。リポジトリにissueテンプレートがあればそちらを優先する。issueを実装する作業（issue-to-pr）やPRのレビュー（pr-review）には使わない。

Discover and use registered local app MCP services through Universal Tools. Use when the user asks for a capability from an app registered with this broker.

Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the agentic benchmark averages. One-shot display.

Quick reference for ponytail's modes, skills, and commands. One-shot display.

Harvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

Surveys a repository's documentation and code to produce a scouting report and architecture document. Use when assessing a codebase before planning or onboarding.

Quality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.

Interviews users to clarify requirements and produce a phased architecture and implementation plan. Use when scope is unclear or before implementation.

Reviews diffs against repository architecture, conventions, correctness, security, and best practices. Use when assessing code changes or a pull request.

全面评审并重建知识快照，保留稳定业务身份及人工材料；只有明确选中的内容才允许修改。

Validate and package a Dramagic 3.0 character release from existing manifest and artwork, or convert a legacy 2.0 manifest with explicit author/package/version. Use for import-ready ZIP assembly, missing-reference troubleshooting and release checks. Do not generate artwork unless the user also requests it.

using-modus 确认当前代码任务影响长期知识后，执行最小语义修订；机械检查只提供待评审候选。

Windows / macOS 本地微信 (WeChat) 与钉钉 (DingTalk) 聊天记录、通讯录、群聊与文件检索 MCP 服务运维管理指南。当需要初始化离线数据库、提取微信解密密钥 (wechat-init)、离线同步钉钉数据库 (dingtalk-init)、检索聊天历史/周报/工时，或在一键彻底清理导出的解密数据与缓存 (im-clean) 时使用。

用于开发、评审、排障和解释 Modus 框架自身，以及基于其源码写文章、技术方案或分享材料。按项目概览、模块所有权、实现契约和验证入口渐进加载；以 modus-open 的 Python 版本为知识基线。普通业务项目使用 Modus 的任务应读取该项目的 using-modus。

Structured triage → mitigation → root-cause flow for live production incidents. Use when a running system is degraded or down (errors, latency, outages) and you need to restore service safely and then find the cause.

AlphaCut의 템플릿·자막·쇼츠 편집 기능을 실제 화면과 공개 자산으로 조사하거나, 고니 작업에서 확인된 AlphaCut 사용법을 재현할 때 사용한다.

Check that every tool a profile needs is installed and recent enough (git, GitHub CLI, Node.js, npm, plus the profile's own - e.g. .NET SDK, PowerShell 7, Azure CLI, Power Platform CLI, LocalDB, k6) and give the exact install command per OS for anything missing. Runs automatically at the start of new-project and quality-gate. Use when the user says "check my tools", "what do I need to install", "is my machine ready", or when a command fails with "not recognized" / "command not found".

Build a sync from a SaaS product to customers' Dynamics 365 / Dataverse environments and Customer Insights - Journeys (multi-tenant app with admin consent and an application user, Web API upserts, contact matching, leads, timeline notes, custom triggers, marketing lists, deep links), tested against a stand-in and a marked sandbox. Use when the owner asks for a Dynamics 365, Dataverse, Power Platform or Customer Insights - Journeys integration.

고니 GitHub 저장소를 확인하고 SCV·Graphify 개발 작업을 이어갈 때 사용한다. 저장소 위치 확인, 도구 점검, 코드 관계 질의, 작업 기억 기록을 돕는다.

Full accessibility pass to WCAG 2.2 AA - axe-core through Playwright over every main page in light and dark at 1440/390 (and 320 for reflow), probes for skip link, one h1, lang, visible and unobscured focus, 24px targets and sideways scrolling, a keyboard script for dialogs/drawers/tabs, manual checks (text spacing, zoom, dragging alternatives, accessible authentication), contract tests for shared components and theme contrast, fixes, known limitations with reasons and an accessibility statement page. Use when the user asks for an "accessibility pass", "WCAG", "a11y audit", "screen reader", or before the first public release.

Use when someone asks for a new Hairline figure, or runs /hairline-create with an idea. Draws one isometric line figure that answers the pointer, in the style and on the engine of @lucasmarkes/hairline, and hands it over as a single self-contained HTML file.

Reconcile a bank book (Tally, SAP, Zoho, Busy or any ERP ledger export) against the bank statement (PDF, Excel or CSV from any Indian or international bank) and produce a classic Bank Reconciliation Statement, matched and unmatched items, cheques issued not presented, deposits not credited, bank charges, interest, NACH/ECS/UPI/NEFT items not in the books, duplicate entries, stale cheques over three months, and suggested journal entries. Ends with a RECONCILED / RECONCILED-WITH-ITEMS / DOES-NOT-CLOSE verdict. Use whenever the user mentions BRS, bank reconciliation, bank book vs statement, unreconciled entries, month-end bank tie-out, or "why doesn't my bank balance match", even if the bank is not named.

Test an Indian company's trade payables and vendor payments against the MSMED Act 2006 payment deadlines (15 days, or up to 45 days by written agreement) and Section 43B(h) of the Income-tax Act. Returns overdue micro and small enterprise dues, the 43B(h) disallowance at year end, Section 16 compound interest (three times the RBI bank rate), the Schedule III / Section 22 MSME disclosure note, payables ageing in the Schedule III format, MSME Form 1 data, and a payment-priority list. Ends with a SAFE / PAY-BEFORE-31-MARCH / DISALLOWANCE verdict. Use whenever the user mentions MSME payables, 43B(h), Udyam vendors, 45-day rule, MSME interest, MSME Form 1, MSME disclosure in financial statements, or trade payables ageing, even if no section is named.

Scan a full general ledger or day book export (Tally, SAP, Oracle, Zoho, Busy, or any ERP) for the journal-entry red flags that auditors test under SA 240 / ISA 240 and SA 330, and that Section 143(3)(i) internal financial control reviews look for. Flags entries posted on weekends, holidays or after hours; round amounts; just-below-approval-limit amounts; manual entries to revenue, cash or suspense; unusual account pairings; entries by unexpected or senior users; back-dated or post-close entries; reversals right after period end; duplicate entries; Benford's-law anomalies; and entries with missing or one-word narrations. Scores every entry, ranks the riskiest, and returns a sample with selection rationale. Ends with a LOW / ELEVATED / HIGH risk verdict. Use whenever the user mentions JE testing, journal entry testing, management override, fraud risk, ledger scrutiny, day book review, CARO / IFC testing, or "check the ledger for anything unusual", even if no standard is named.