Use for ast-grep: ast-grep run, sg scan, sg test, sg new, new rule, sgconfig.yml, inline-rules, stdin, json, optional chaining, rule catalog, meta variables, pattern objects, nthChild stopBy, range field, metadata url, caseInsensitive glob, severity off, include metadata, rule order, kind pattern, positive rule, kind esquery, debug-query, static analysis, tree-sitter parser, pattern yaml api, search rewrite lint analyze, textual structural, ast cst, named unnamed, kind field, ambiguous pattern, effective selector, meta variable detection, lazy multi, strictness smart, relaxed signature, string fix, fix config, expandEnd, replace substring, toCase separatedBy, rewriter, rewrite joinBy, find patch, barrel import, ruleDirs testConfigs, libraryPath languageSymbol, dynamic injected, custom language, TREE_SITTER_LIBDIR, language injection, styled components, language alias, languageGlobs, expandoChar, napi parse, python api, programmatic API.
Conventional Commits style guide + safety rules. Pull this before any git commit so the message shape and staging rules stay consistent.
- 📁 rules/
- 📄 AGENTS.md
- 📄 metadata.json
- 📄 README.md
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.
This skill should be used when the user asks to "organize the project rules", "clean up scattered documentation", "把规则迁移到 skills 目录", "优化 skill 路由", "提高 description 命中率", or "减少薄壳重复维护". Activate when a SKILL.md is too large, rules are duplicated across agent entry files, task routing or trigger_examples miss natural user language, or templates / thin shells / validation scripts need drift-resistant maintenance.
Use when creating or modifying OpenCode rules (.md/.mdc files) that customize agent behavior. Trigger when user wants to create a rule, codify repeated instructions, persist guidance across sessions, or scope rules to specific files, prompts, environments, or workflows.
Author custom Falco rules for Prempti — the policy and visibility layer for AI coding agents. Use this skill whenever the user asks to create, edit, or debug rules that control what coding agents (Claude Code, etc.) can do. Triggers on phrases like "add a rule", "block this tool", "deny access to", "allow writes to", "create a security policy", "custom Falco rule for coding agent", or any request to modify files under rules/user/. This skill covers the coding_agent plugin source and its specific fields — NOT syscall rules.
Identify conflicting rules between two lists of extracted rules. Use this skill when comparing a skill's rules against another skill's rules or against agent config rules (CLAUDE.md, GEMINI.md, etc.).
Loads coding rules from Qodo most relevant to the current coding task by generating a semantic search query from the assignment. Use when Qodo is configured and the user asks to write, edit, refactor, or review code, or when starting implementation planning. Skip if rules are already loaded.
- 📁 .gemini/
- 📁 .github/
- 📁 agent-skill/
- 📄 .gitattributes
- 📄 .gitignore
- 📄 AGENTS.md
Guide for developing and maintaining the Hubitat MCP Rule Server — a Groovy-based MCP server running natively on Hubitat Elevation hubs, exposing 90 tools (35 on tools/list via category gateway proxy) for device control, virtual device management, room management, rule automation, hub admin, file management, app/driver management, installed-app visibility, Rule Machine interoperability, native rule CRUD, and Developer Mode self-administration.
Designs stable, well-documented APIs and module interfaces. Use when creating REST/GraphQL endpoints, defining contracts between modules, or changing public interfaces. The wire-format SSOT — response envelope, HTTP status codes, validation taxonomy, payload naming — lives in `.agents/rules/api-conventions.md`; this skill shows authors how to apply it. --- # Skill: api-and-interface-design Process guidance for designing interfaces that are hard to misuse — REST APIs, GraphQL schemas, module boundaries, and component props. The wire-format conventions (envelope shape, status codes, validation taxonomy, payload naming) live in [`.agents/rules/api-conventions.md`](../../../rules/api-conventions.md), which is the SSOT. This skill shows authors **how** to apply those rules; read the rule file for the **what**. Security validation guarantees live in [`security-baseline.md`](../../../rules/security-baseline.md); test-layer scope lives in [`testing-standards.md`](../../../rules/testing-standards.md). ## When to Use - Designing new API endpoints. - Defining module boundaries or contracts between teams. - Creating component prop interfaces. - Establishing database schema that informs API shape. - Changing existing public interfaces. ## 1. Hyrum's Law — Be Intentional About Exposure > With a sufficient number of users of an API, all observable behaviors of > your system will be depended on by somebody, regardless of what you promise > in the contract. Every observable behavior — undocumented quirks, error message text, timing, ordering — becomes a de facto contract once users depend on it. Implications: - **Be intentional about what you expose.** Every observable behavior is a potential commitment. - **Don't leak implementation details.** If users can observe it, they will depend on it. - **Plan for deprecation at design time.** See `deprecation-and-migration` for how to safely remove things users depend on. - **Tests are not enough.** Even with perfect contract tests, "safe"
- 📁 references/
- 📄 rules.index.json
- 📄 SKILL.md
React Native and Expo best practices. Routes through rules.index.json (118
- 📁 examples/
- 📁 tests/
- 📁 workflows/
- 📄 SKILL.md
Execute agent-centric reviews on all rules in rules/ directory and generate prioritized improvement report
