Loading...
Loading...
Found 17 Skills
Skill for creating custom lint rules by leveraging the existing linter ecosystems of various programming languages. This is a linter designed for AI Agents rather than humans, and its error messages function as correction instruction prompts for AI. Create custom rules in the `lints/` directory using standard methods for each language, including Rust (dylint), TypeScript/JavaScript (ESLint), Python (pylint), Go (golangci-lint), etc. Use this skill in the following scenarios: (1) When you want AI to enforce project-specific coding rules; (2) When you want to create lint rules that output AI-readable correction instructions when violations occur; (3) When you want to enforce naming conventions, structural patterns, and consistency rules through AI-driven linting. Triggers: "Create a linter rule", "Add a lint rule", "Enforce this pattern", "AI linter", "Custom lint", "Code rules", "Naming rules", "Structural rules", "create a linter rule", "add a lint rule", "enforce this pattern", "AI linter".
Synthesize a recurring code-review rule into a custom lint rule — gated by an independent soundness test that abstains rather than ship a checker it can't prove sound
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
Unified Obsidian skill: plugin development AND desktop automation. Use when building or validating an Obsidian plugin (boilerplate, 27 ESLint rules, submission), or when driving desktop Obsidian from the terminal via the official CLI, obsidian:// URIs, or kepano/obsidian-skills markdown/bases/json-canvas patterns. Triggers on: obsidian plugin, obsidian cli, obsidian automation, obsidian development, obsidian eslint, obsidian submission, obsidian markdown, obsidian bases, json-canvas, obsidian vault, obsidian URI, obsidian commands. Installable as a plugin: claude plugin marketplace add akillness/oh-my-skills
Implement React Doctor rules from a validated contract. Use when writing oxlint rules, planning syntax or control-flow detection, designing adversarial tests, reusing syntax tree utilities, or updating rule registration.