_archive
Archived skills
medusa
Medusa rules and best practices. These rules should be used when building applications with Medusa.
starknet-react-rules
Specific rules for Starknet React projects, focusing on blockchain integration.
strategic-planning-with-pseudocode
Rules that enforce to use pseudocode before implementation
artifact-updater
[DEPRECATED] Route through type-specific updaters: skill-updater, agent-updater, workflow-updater.
aceternity-ui-configuration
Specifies that Aceternity UI dependencies should be considered during code generation or modification.
activities
Coding standards and best practices for Temporal activities.
framer-motion-rules
Defines framer motion is being used for animations
additional-htmx-and-flask-instructions
Provides additional instructions for HTMX and Flask, primarily related to templating.
admin-interface-rules
Rules for the Admin interface functionalities
agp-router-rules
Rules for using the Agp Router.
alpine-js-usage-rules
Guidelines for using Alpine.js for declarative JavaScript functionality.
angular-expert
Angular framework expert including components, services, RxJS, templates, and testing
apiresponse-class
Structure of ApiResponse class.
artifact-publisher
Publish and share artifacts to the project. Use when a user wants to save, share, or finalize generated artifacts.
assistant-behavior-rules
AI assistant behavior rules including response formatting and interaction patterns
astro-expert
Astro framework expert including components, content collections, and integrations
asynchronous-programming-preference
Favors the use of async and await for asynchronous programming in Python.
authentication-flow-rules
OAuth 2.1 compliant authentication flows (MANDATORY Q2 2026). PKCE required for ALL clients, Implicit Flow removed, modern token security.
automation-script-rule
Sets guidelines for creating or modifying automation scripts within the project.
babel-configuration-for-nativewind
Specifies the correct Babel configuration for NativeWind to ensure proper processing and avoid conflicts.
backend-expert
Backend development expert including server architecture, middleware, and data handling
beefreesdk
Guidelines and best practices for building applications with [Beefree SDK](https://docs.beefree.io/beefree-sdk), including installation, authentication, configuration, customization, and template mana
brainstorming
Socratic design refinement before implementation. Use when planning creative work or designing features.
browser-api-usage-rules
Rules for effectively utilizing Chrome's browser APIs, including error handling and scheduling tasks.
bug-handling-with-todo-comments
Specifies the usage of TODO comments to outline problems or bugs encountered in existing code, regardless of file type.
build-notes-file-rules
Enforces rules for creating and managing build notes files within the /ProjectDocs/Build_Notes/ directory, including naming conventions, content structure, and update frequency.
check-x-md-content-rule
This rule reminds the AI to check the x.md file for the current file contents and implementations.
chrome-extension-expert
Browser extension expert including Chrome APIs, manifest, and security
ckeditor-rules
Defines CKEditor is being used for text editing
class-based-state-management
Enforces the use of classes for complex state management (state machines) in Svelte components. Applies specifically to `.svelte.ts` files.
cloud-native-and-kubernetes-expertise-rules
Ensures the documentation demonstrates a high level of expertise in cloud-native technologies and Kubernetes.
codebase-integration
Structured workflow for integrating external codebases into agent-studio. Ensures skills, agents, templates, and workflows are properly imported with mandatory router updates.
collaboration-and-version-control-rules
Promotes effective collaboration and version control practices for managing the documentation.
comment-usage
This rule dictates how comments should be used within the codebase to enhance understanding and avoid clutter.
commit-message-guidelines
Provides guidelines for creating conventional commit messages, ensuring they adhere to a specific format and are concise.
commit-validator
Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.
communication-and-problem-solving
Guidelines for communication, problem-solving and platform thinking applying to all files.
communication-tone
Establish a professional and concise style for all AI communication and output.
computer-use
Claude Computer Use tool integration for desktop automation. Enables Claude to interact with computer environments through screenshots, mouse control, keyboard input, and application automation in sandboxed environments.
conditional-encapsulation
This rule enforces encapsulating nested conditionals into functions to improve clarity.
content-creation-rules
Applies guidelines for creating high-quality documentation content, focusing on clarity, accuracy, and relevance.
context-files-rules
Specifies rules for managing context files, including the master project context and supplementary files, emphasizing stability and change management.
continuous-improvement-focus
Emphasizes continuous improvement by suggesting process improvements and looking for opportunities to simplify and optimize code and workflows. This rule promotes a culture of ongoing refinement.
convex-development-general
Applies general rules for Convex development, emphasizing schema design, validator usage, and correct handling of system fields.
custom-slash-commands
Enables custom slash commands, such as /commit, to generate conventional commit messages.
dependencies-management-rules
Mandates the usage of UV when installing dependencies to ensure consistency and efficiency across all environments.
detailed-docstrings
Requires detailed Google-style docstrings for all functions, methods, and classes.
directory-naming-convention
Defines the directory naming convention.
dispatching-parallel-agents
Concurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
Page 1 of 12 · 575 results