Loading...
Loading...
Found 57 Skills
Run Semgrep static analysis scans and create custom detection rules. Use when asked to scan code with Semgrep, find security vulnerabilities, write custom YAML rules, or detect specific bug patterns.
L3 Worker. Reviews task implementation for quality, code standards, test coverage. Creates [BUG] tasks for side-effect issues found outside task scope. Sets task Done or To Rework. Usually invoked by ln-400 with isolated context, can also review a specific task on user request.
Configure GitHub Copilot with custom instructions. Use when setting up .github/copilot-instructions.md, customizing Copilot behavior, or creating repository-specific AI guidance. Triggers on Copilot instructions, copilot-instructions.md, GitHub Copilot config.
Hierarchical exception system with HTTP status codes, machine-readable error codes, and structured responses for consistent API error handling across all endpoints.
Batch check whether Skills comply with best practice specifications; automatically verify dimensions such as naming, preface section, structure, file cleanup, and dependencies; support single or batch checks; generate detailed inspection reports; suitable for quality verification after Skill development is completed
Generate frontend page structures based on standardized Anatomy specifications; proactively ask users to select generation modes (Unsupervised/Supervised), and support automatic generation of Wrapper, Content, and Optional Store modules
Unified management of SVG icons in React TypeScript projects; supports icon component encapsulation, naming conventions, and migration guidance; applicable to scenarios such as project icon refactoring, new project icon specification formulation, and icon maintenance optimization
Builds, restructures, and standardizes React components according to project conventions (placement, folder/file naming, exports, props patterns). Use when adding components or when reorganizing existing components during refactors, migrations, or component moves.
Titanium SDK architecture and implementation expert. Use when designing, reviewing, analyzing, or examining Titanium project structure (Alloy or Classic), creating controllers/views/services, choosing models vs collections, implementing communication patterns, handling memory cleanup, testing, auditing code, or migrating legacy apps. Automatically identifies project type.
Assist developers in initializing, writing, and standardizing Forguncy plugin code, supporting the development of server-side commands and front-end cell types.
Reference these patterns to validate consistency across the ecosystem. Use when creating new skills or hooks that need consistent patterns, implementing validation logic, setting up error handling, creating test scaffolding, referencing standard workflow structures. Do not use when pattern is specific to one skill only. DO NOT use when: pattern is still evolving - wait for stability. DO NOT use when: pattern is context-dependent requiring variations.
Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches