Loading...
Loading...
Found 25 Skills
Example skill template. Replace this description with keywords and triggers for your actual skill. This description determines when the skill auto-loads based on conversation context.
Auto-extract patterns from coding sessions, track corrections, and build reusable knowledge with confidence scoring
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
Apply production-ready Databricks SDK patterns for Python and REST API. Use when implementing Databricks integrations, refactoring SDK usage, or establishing team coding standards for Databricks. Trigger with phrases like "databricks SDK patterns", "databricks best practices", "databricks code patterns", "idiomatic databricks".
Share a single global instance throughout your application to manage global state.
Intercept and control interactions with target objects using JavaScript Proxies.
Example project-specific skill template based on a real production application.
Research how production Rails apps solve architectural problems using the Real World Rails repository. Use when the user wants to know how other apps handle something, find patterns, or compare approaches. Triggers on "rails patterns", "how do other apps", "real world rails", "research how apps do".
Rails code patterns and conventions following rubocop-rails-omakase style.
Reference FilamentPHP v4 documentation for patterns, methods, and implementation examples
Scan codebase for security vulnerabilities including secrets, insecure dependencies, and unsafe code patterns. Use when performing automated security scans.
Organize reusable programming patterns / library usages / technical skills that answer "To do this kind of thing, the correct approach is this" into a prescriptive reference library, which can be retrieved and reused as needed during feature-design and issue-analyze phases. Three types: pattern (design patterns, programming idioms), library (usage and pitfalls of a certain library/framework), technique (specific operation skills / command recipes). Trigger scenarios: When the user says "record a trick", "this usage is worth recording", "tricks", "record library usage", or when a skill worth archiving is discovered during feature-design / issue-analyze phases and actively pushed. Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / decisions / explore.