Coding & Development

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.

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".

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.

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.

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.

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.

在本地为合成生物学和 iGEM 项目建立带项目边界、版本与行号出处的资料账本，并进行可解释的关键词检索。适用于团队资料归档；不提供云端同步、语义搜索或多用户鉴权。

为合成生物学概念、论文和技术方案建立可追溯的证据卡，解释机制、适用范围与不确定性，并按公开来源介绍中国研究者。适用于科学答疑与研究研判；不替代实验审批或赛事规则核验。

按参赛年份和用户角色回答 iGEM 报名、赛程、安全、交付物、评审与学习问题，提供中英摘要和可核验官方入口。适用于赛事辅导；不代表 iGEM 官方，也不把预检查写成审批结果。

把合成生物学研究构想、iGEM项目、课程或科普需求转成带依赖、证据门槛和验收标准的执行蓝图。适用于计划设计与复盘；不负责替用户确认科学结论或当年赛事规则。

把已校核的合成生物学授课、主持或答辩内容组织成带触发点、证据和交接提示的中文现场卡片，支持长文分页、多人分套与来源索引，输出可打印 HTML 或 PDF。

>- Deploy the current app to staging — runs tests, builds, asks for human confirmation, then runs the staging deploy script and a health smoke check. Use when the user wants to deploy to staging (demo target: ex_staging).

>- Audit npm dependencies for vulnerabilities and verify tests still pass. Use for Node/JavaScript packages (package.json). For Python apps with requirements.txt, use the audit-python skill instead.

Turn the main session into a dispatcher that never blocks. Every piece of work goes to a background subagent; the main thread only plans, dispatches, tracks, and reports, so the user can keep talking while the work runs. Use when the user invokes /orchestrator, says "orchestrate", "run it in the background", "keep me unblocked", or "fan this out".

>- Audit Python dependencies with pip-audit and verify the app still works. Use when the user asks for pip-audit, Python CVE check, or audit on a requirements.txt project (e.g. ex_app). For Node/npm, use the audit skill.

Sets up and maintains a Markdown wiki inside a repository that agents keep current, in the "LLM wiki" style. Use when asked to create a project wiki, add a source to it, answer a question from it, update it after a code change, check it for broken links or stale pages, or reorganize it.

>- Draft or create GitHub Feature issues using the repo's feature template. Use when the user asks for a feature issue, epic, or user-story-driven work item, or when type is feature in issue frontmatter.

Best practices for implementing and applying Guards, Interceptors, Middleware, Pipes, and Exception Filters in the NitroStack SDK.

>- Draft or create GitHub Bug issues using the repo's bug template. Use when the user reports a defect, asks for a bug issue, or when type is bug in issue frontmatter.

Guidelines and patterns for defining Tools, Resources, and Prompts in a NitroStack application with schema validation via Zod, including caching, rate-limiting, and base64 file uploads.

Keeps commits few and messages short. Use before a commit, before a push, when commits pile up during a fix, or when the commit-check hook warns.

Turn a rough idea, a user complaint or an incident into a committed intent.md by interviewing the person who has the problem. Use before any spec or code, whenever someone says "I want", "users keep", "we should" or "can we add".

Apply the user's requested conversational style when chatting, advising, checking assumptions or reviewing academic work. Use direct evidence-based reasoning, natural Vietnamese tao/mày when appropriate, occasional light teasing, and a fair separate review of your own work. Adapt humor to context; preserve the required register in formal deliverables. Do not turn confidence, personality or the user's agreement into factual evidence.