Loading...
Loading...
Found 25 Skills
프로젝트의 구조를 변경해야하거나, 새롭게 구현을 진행할 때 해당 구조를 기반으로 구현할 수 있도록 한다. 자동적으로 해당 구조를 기반으로 구현을 하되, 사용자가 명시적으로 구조를 변경하고자 할 때는 사용자의 의견을 반영한다. 구조에 대한 자세한 설명은 reference/FSD.md를 참고한다.
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.
Understand Slidev project structure and configuration. Use this skill to configure themes, addons, and customize your presentation setup.
This skill should be used when the user asks to "create a django project", "new django app", "django models", "django forms", "set up django", "configure django settings", or mentions Django project structure, model organization, or Dynaconf configuration. Provides opinionated Django development patterns with 1-file-per-model organization and consistent naming conventions.
Create Scratch project with TypeScript using Hikkaku; use when the user asks how to build or structure a Scratch project in this repo.
Architecture principles, module boundaries, folder structure, and project type profiles
Clean up code, remove dead code, and optimize project structure. Use when user wants to clean codebase, remove unused code, or optimize imports.
Creative writing project architecture — concept mapping, thematic structure, outlining, and strand interweaving. Helps the user see the shape of their project. Use when structuring a new project, reorganizing an existing one, or mapping how narrative, art-as-code, and theory interweave.
Implement PostHog reference architecture with best-practice project layout. Use when designing new PostHog integrations, reviewing project structure, or establishing architecture standards for PostHog applications. Trigger with phrases like "posthog architecture", "posthog best practices", "posthog project structure", "how to organize posthog", "posthog layout".
Enforces the CodeBelt TypeScript and React code style guide for project structure, naming conventions, component patterns, service patterns, testing, and TypeScript rules. Use when writing, reviewing, or refactoring TypeScript or React code, creating new files or components, organizing project directories, writing tests, defining Zod schemas, or when the user mentions code style, conventions, linting, file organization, or naming patterns.
Senior Python developer. Use when writing, reviewing, or refactoring Python code. Enforces idiomatic Python, type hints, and modern patterns.
Applies best practices for logging, project structure, and environment variable usage specifically to the main application file.