Loading...
Loading...
Found 31 Skills
Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.
Skill for using Astro projects. Includes CLI commands, project structure, core config options, and adapters. Use this skill when the user needs to work with Astro or when the user mentions Astro.
Codebase orientation. Use FIRST when exploring code, finding files, or understanding project structure.
Perform comprehensive Rust code quality reviews against best practices for async Rust, error handling, testing, and project structure
Reverse import existing novels. Parse written novels (unfinished or completed) into a standard project directory structure, compatible with the subsequent writing workflow of story-long-write. Internally reuse the deep analysis pipeline of story-long-analyze. Trigger methods: /story-import, "Import Novel", "Reverse Parse", "Import", "Import My Book"
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"
Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
Complete project architecture and structure guide. Use when exploring the codebase, understanding project organization, finding files, or needing comprehensive architectural context. Triggers on architecture questions, directory navigation, or project overview needs.
Go application architecture with net/http 1.22+ routing, project structure patterns, graceful shutdown, and dependency injection. Use when building Go web servers, designing project layout, or structuring application dependencies.
High-level architecture decisions, patterns, and project structure. Use when user asks about architecture decisions, project structure, pattern selection, or mentions how to organize, which pattern to use, best practices, architecture.
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.
Applies best practices for logging, project structure, and environment variable usage specifically to the main application file.