custom-project-standards
Hệ thống tiêu chuẩn dự án đa năng (Standard Platform). Hỗ trợ Frontend, Backend, DevOps với nhiều tùy chọn ngôn ngữ/framework.
Best use case
custom-project-standards is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Hệ thống tiêu chuẩn dự án đa năng (Standard Platform). Hỗ trợ Frontend, Backend, DevOps với nhiều tùy chọn ngôn ngữ/framework.
Teams using custom-project-standards should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/custom-project-standards/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How custom-project-standards Compares
| Feature / Agent | custom-project-standards | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Hệ thống tiêu chuẩn dự án đa năng (Standard Platform). Hỗ trợ Frontend, Backend, DevOps với nhiều tùy chọn ngôn ngữ/framework.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Custom Project Standard Platform (v2.1)
> **OPERATING MECHANISM:**
> 1. **Auto-Config:** Checks for `agent-project-config.md` in the workspace root. If found, loads Context/Role from there.
> 2. **Wizard Mode:** If NO config file is found, asks the User to determine Context & Stack.
---
## 1. Setup & Context Protocol (Configuration Protocol)
### Step 0: Check Config (Highest Priority)
Before asking the user, search for the `agent-project-config.md` file in the root directory.
**If found:**
Read the Frontmatter of the file to determine:
- `project_type` -> Determine Domain (Frontend/Backend...)
- `tech_stack` -> Determine Stack (NestJS/NextJS...)
- `role_mode` -> Determine Persona (Architect/Implementer...)
> **Note:** If Config exists, **SKIP** Steps 1 and 2 below, proceed directly to Step 3 (Load Context).
**If NOT found:**
Execute "Wizard" mode (Steps 1 & 2), then **propose the user to create a config file** for future sessions.
### Step 0.5: Analyze Environment (Existing Codebase Protocol)
Before applying any rigid rules or installing new packages, the Agent **MUST READ** the dependency management files (`package.json`, `go.mod`, `composer.json`, `requirements.txt`).
**Principles:**
1. **Respect Legacy:** If the project already uses a specific library (e.g., `TypeORM` instead of `Prisma`), **USE IT**. Do not suggest switching unless explicitly requested.
2. **Kit Default:** Only recommend the Kit's preferred packages (from `tech-stack.md`) if the project is brand new or lacks that specific capability.
### Step 1: Determine Project Type (Domain) - *Wizard Mode*
Ask the User or auto-detect:
* [ ] **Frontend**
* [ ] **Backend**
* [ ] **DevOps**
### Step 2: Determine Language/Framework (Stack) - *Wizard Mode*
Based on the Domain, further determine:
* **Frontend:** Next.js | Vue | React Native
* **Backend:** NestJS | Python (FastAPI) | Go | Laravel
* **DevOps:** Docker | K8s | AWS
### Step 3: Load Context (Important)
After determination (via Config or Wizard), the Agent **MUST READ** the following documents in order:
1. **Core Principles (Global):** `rules/standards/design-principles.md` (MUST READ FIRST)
2. **Domain Rules:** (e.g., `rules/backend/general.md`)
3. **Stack Rules:** (e.g., `rules/backend/nestjs/convention.md`)
4. **Role Mode (If available):** (e.g., `rules/roles/architect.md`)
> 💡 **Example:** Config is `Backend` + `NestJS`:
> -> Agent reads `rules/standards/design-principles.md`
> -> Agent reads `rules/backend/general.md`
> -> Agent reads `rules/backend/nestjs/convention.md`
---
## 2. Rules Map
### 🎨 Frontend
| Stack | Rule File | Template |
|-------|-----------|----------|
| **General** | `rules/frontend/general.md` | - |
| **Next.js** | `rules/frontend/nextjs/convention.md` | `templates/frontend/nextjs/` |
| **Vue/Nuxt** | `rules/frontend/vue/convention.md` | `templates/frontend/vue/` |
### ⚙️ Backend
| Stack | Rule File | Template |
|-------|-----------|----------|
| **General** | `rules/backend/general.md` | - |
| **NestJS** | `rules/backend/nestjs/convention.md` | `templates/backend/nestjs/` |
| **Laravel** | `rules/backend/laravel/convention.md` | - |
| **Go** | `rules/backend/go/convention.md` | - |
| **Python** | `rules/backend/python/convention.md` | `templates/backend/python/` |
### 🚀 DevOps
| Stack | Rule File |
|-------|-----------|
| **Docker** | `rules/devops/docker-standard.md` |
| **CI/CD** | `rules/devops/cicd-standard.md` |
---
## 3. Installation Guide
In case the User requests *"Create a new project"*, follow these steps:
1. **Ask User:** "Do you want to create a Frontend or Backend project? Which language?"
2. **Confirm:** "I will create a **Next.js** project following **Custom Standard v2**."
3. **Execute:**
* Copy structure from `templates/frontend/nextjs/` (if available)
* Create `README.md` with content from `rules/frontend/nextjs/convention.md`
* Install required dependencies (check `tech-stack.md` in the subfolder).Related Skills
customize
Add new capabilities or modify MicroClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.
customer-meeting-intelligence
Comprehensive meeting intelligence system for customer-facing calls. Provides proactive pre-call briefings with account context, post-meeting action item extraction with draft approval, and thread continuity. Use when you need: (1) automated morning briefings for customer meetings, (2) post-meeting action item extraction from Fellow.ai and Gmail Gemini notes, (3) draft approval workflow before posting meeting notes, (4) customer context gathering including billing, support tickets, and communication history, (5) meeting follow-up automation with account intelligence.
custom-plugin-flutter-skill-backend
1500+ lines of backend integration mastery - REST APIs, GraphQL, WebSockets, authentication, Firebase, error handling with production-ready code examples.
create-spring-boot-kotlin-project
Create Spring Boot Kotlin Project Skeleton
create-spring-boot-java-project
Create Spring Boot Java Project Skeleton
coding-standards
Provides coding standards for React Native — performance patterns, consistency rules, and clean React architecture. Use when writing, modifying, or reviewing code.
claude-flow-hook-customizing
Use this skill when creating, optimizing, or maintaining claude hooks.
chatgpt-project-architect
Use cuando necesites crear o mejorar instrucciones de proyecto ChatGPT, diseñar system prompts, definir agentes conversacionales, estructurar modos y comandos, implementar anti-injection, o validar calidad de project instructions. Keywords: chatgpt project, system prompt, project instructions, agent design, prompt engineering, anti-injection, command shortcuts, agent modes.
cc-skill-project-guidelines-example
Project Guidelines Skill (Example)
cc-skill-coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
building-streamlit-custom-components-v2
Builds bidirectional Streamlit Custom Components v2 (CCv2) using `st.components.v2.component`. Use when authoring inline HTML/CSS/JS components or packaged components (manifest `asset_dir`, js/css globs), wiring state/trigger callbacks, theming via `--st-*` CSS variables, or bundling with Vite / `component-template` v2.
awesome-copilot-root-create-spring-boot-java-project
Create Spring Boot Java Project Skeleton Use when: the task directly matches create spring boot java project responsibilities within plugin awesome-copilot-root. Do not use when: a more specific framework or task-focused skill is clearly a better match.