Skip to content

Commit f0febab

Browse files
zbeyenszbeyens
committed
taskmaster
1 parent 59db8ae commit f0febab

File tree

31 files changed

+3084
-0
lines changed

31 files changed

+3084
-0
lines changed

‎apps/www/src/registry/components/editor/plugins/basic-blocks-kit.tsx‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ export const BasicBlocksKit = [
1919
H1Plugin.configure({
2020
node: {
2121
component: H1Element,
22+
type: 'heading1',
2223
},
2324
rules: {
2425
break: { empty: 'reset' },

‎packages/utils/src/react/plugins/BlockPlaceholderPlugin.tsx‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,27 @@ export const BlockPlaceholderPlugin =
7272

7373
const [element, path] = entry;
7474

75+
// const getPlaceholder = (node: TElement) => {
76+
// if (node?.listStyleType) {
77+
// switch (node.listStyleType) {
78+
// case 'disc':
79+
// return 'List';
80+
// break;
81+
// case 'decimal':
82+
// return 'List';
83+
// break;
84+
// case 'todo':
85+
// return 'To-do';
86+
// break;
87+
// }
88+
// }
89+
90+
// const key = getPluginKey(editor, node.type);
91+
// if (!key) return;
92+
93+
// return placeholders?.[key];
94+
// }
95+
7596
const placeholder = Object.keys(placeholders).find(
7697
(key) => editor.getType(key) === element.type
7798
);

‎templates/plate-template/.claude/commands/architect.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
Deeply reflect upon the changes being asked and analyze existing code to map the full scope of changes needed.
2+
3+
Think deeply about the scale of what we're trying to build so we understand how we need to design the system. Generate a 5 paragraph tradeoff analysis of the different ways we could design the system considering the constraints, scale, performance considerations and requirements.
4+
5+
Before proposing a plan, ask 4-6 clarifying questions based on your findings to assess the scale of the system we're trying to build. Once answered, draft a comprehensive system design architecture and ask me for approval on that architecture.
6+
7+
If feedback or questions are provided, engage in a conversation to analyze tradeoffs further and revise the plan - once revised, ask for approval again.
8+
9+
Once approved, work on a plan to implement the architecture based on the provided requirements.
10+
11+
If feedback is provided, revise the plan and ask for approval again. Once approved, implement all steps in that plan.
12+
13+
After completing each phase/step, mention what was just completed and what the next steps are + phases remaining after these steps

‎templates/plate-template/.claude/commands/create-app-design-document.md‎

Lines changed: 140 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,140 @@
1+
# Rule: Generating an Application Design Document
2+
3+
> $ARGUMENTS
4+
5+
## Goal
6+
7+
To guide an AI assistant in creating a comprehensive Application Design Document in Markdown format, based on deep analysis of an existing codebase and user input. The document should provide a high-level overview of the application's architecture, core features, user experience, and business logic while remaining technology-agnostic and focused on the "what" rather than the "how".
8+
9+
## Process
10+
11+
1. **Receive Initial Prompt:** The user requests an app design document for their existing project or wants to document a new application concept.
12+
2. **Deep Codebase Analysis:** Thoroughly analyze the existing codebase to understand:
13+
- Application structure and main features
14+
- User flows and business logic
15+
- Data models and relationships (conceptual, not technical)
16+
- Authentication and authorization patterns
17+
- Core functionalities and user interactions
18+
- Integration points and external services
19+
3. **Ask Clarifying Questions:** Before writing the document, ask 5-8 targeted questions based on the codebase analysis. **ALWAYS start with project stage and development priorities questions first**, then focus on understanding the application's purpose, target users, and business goals. Provide lettered/numbered options for easy response.
20+
4. **Update Project Status:** Based on the project stage answer, update the CLAUDE.md "Project Status" section to reflect current priorities and what AI should/shouldn't care about.
21+
5. **Generate Document:** Create a comprehensive app design document using the structure outlined below.
22+
6. **Save Document:** Save as `app-design-document.md` in the `.taskmaster/docs/` directory.
23+
24+
## Clarifying Questions (Examples)
25+
26+
**CRITICAL FIRST QUESTIONS** - Ask these first to set proper context:
27+
28+
- **Project Stage:** "What stage is your application currently in?"
29+
30+
- a) Pre-MVP (no production deployment yet)
31+
- b) MVP deployed (basic version live)
32+
- c) Production (mature application with users)
33+
- d) Enterprise (large scale, multiple teams)
34+
35+
- **Development Priorities:** Based on the project stage, "What should AI care about vs NOT care about during development?"
36+
- **Pre-MVP example:** Focus on core functionality, security, validation. Skip unit testing, accessibility optimization, performance tuning. Do not care about breaking changes.
37+
- **MVP+ example:** Include testing strategies, accessibility, performance considerations, breaking change management.
38+
39+
**Additional questions** - Adapt these based on the codebase analysis:
40+
41+
- **Application Purpose:** "What is the primary problem this application solves?" or "Who is the target audience and what are their main goals?"
42+
- **Core Value Proposition:** "What makes this application unique compared to existing solutions?"
43+
- **User Types:** "What different types of users interact with this system? (e.g., end users, admins, content creators)"
44+
- **Key User Journeys:** "Can you describe the most important user flows from sign-up to achieving their goals?"
45+
- **Business Model:** "How does this application generate value? (e.g., SaaS, marketplace, content platform)"
46+
- **Integration Requirements:** "What external systems or services does this application need to integrate with?"
47+
- **Security & Privacy:** "What are the key security and privacy requirements for your users?"
48+
- **Scalability Goals:** "What scale are you planning for? (users, data, geographic reach)"
49+
- **Future Vision:** "What major features or capabilities do you envision adding in the future?"
50+
- **Success Metrics:** "How do you measure success for this application?"
51+
52+
## Document Structure
53+
54+
The generated document must follow this high-level structure:
55+
56+
### **Introduction**
57+
58+
- Application overview and purpose
59+
- Target audience and user base
60+
- Core value proposition
61+
- Business context and goals
62+
63+
### **Core Features**
64+
65+
- **Feature Category 1:** (e.g., User Management)
66+
- Purpose and user benefit
67+
- Key functionalities
68+
- User experience considerations
69+
- **Feature Category 2:** (e.g., Content Creation)
70+
- Purpose and user benefit
71+
- Key functionalities
72+
- User experience considerations
73+
- **[Additional feature categories as needed]**
74+
75+
### **User Experience**
76+
77+
- User personas and roles
78+
- Key user journeys and flows
79+
- Interface design principles
80+
- Accessibility and usability considerations
81+
82+
### **System Architecture**
83+
84+
- High-level system components
85+
- Data flow and relationships
86+
- Integration points and external services
87+
- Security and privacy approach
88+
89+
### **Business Logic**
90+
91+
- Core business rules and processes
92+
- Data models and relationships (conceptual)
93+
- Workflow and state management
94+
- Validation and business constraints
95+
96+
### **Future Considerations**
97+
98+
- Planned enhancements and features
99+
- Scalability considerations
100+
- Potential integrations
101+
- Long-term vision and roadmap
102+
103+
## Target Audience
104+
105+
The document should be accessible to:
106+
107+
- **Business stakeholders** who need to understand the application's purpose and capabilities
108+
- **Product managers** planning features and roadmaps
109+
- **Designers** creating user interfaces and experiences
110+
- **New developers** joining the project who need a high-level understanding
111+
- **Technical leaders** making architectural decisions
112+
113+
The language should be clear, business-focused, and avoid technical implementation details.
114+
115+
## Key Principles
116+
117+
1. **High-Level Focus:** Describe WHAT the application does, not HOW it's implemented
118+
2. **User-Centric:** Emphasize user value and experience over technical capabilities
119+
3. **Business Context:** Connect features to business goals and user needs
120+
4. **Technology-Agnostic:** Avoid specific technology mentions (those belong in tech-stack.md)
121+
5. **Future-Oriented:** Consider scalability and evolution of the application
122+
123+
## Output
124+
125+
- **Format:** Markdown (`.md`)
126+
- **Location:** `.taskmaster/docs/`
127+
- **Filename:** `app-design-document.md`
128+
129+
## Final Instructions
130+
131+
1. Do NOT start implementing the document immediately
132+
2. First analyze the codebase deeply to understand the application's structure and purpose
133+
3. **CRITICAL:** Ask project stage and development priorities questions FIRST with lettered/numbered options
134+
4. Based on project stage answer, update both:
135+
- `CLAUDE.md` "Project Status" section with appropriate priorities
136+
- `.cursor/rules/project-status.mdc` with the specific DO/DON'T lists for the determined stage
137+
5. Ask remaining clarifying questions with lettered/numbered options for easy selection
138+
6. Generate a complete document following the structure above, tailored to the project stage
139+
7. Focus on high-level application design, leaving technical implementation details for the tech-stack document
140+
8. After saving, suggest creating a complementary tech-stack document if one doesn't exist

‎templates/plate-template/.claude/commands/create-tech-stack.md‎

Lines changed: 165 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,165 @@
1+
# Rule: Generating a Tech Stack Documentation
2+
3+
> $ARGUMENTS
4+
5+
## Goal
6+
7+
To guide an AI assistant in creating a comprehensive Tech Stack Documentation in Markdown format, based on deep analysis of an existing codebase and user input. The document should provide detailed technical information about technologies, frameworks, libraries, development tools, and implementation patterns used in the project.
8+
9+
## Process
10+
11+
1. **Receive Initial Prompt:** The user requests tech stack documentation for their existing project.
12+
2. **Deep Technical Analysis:** Thoroughly analyze the codebase to understand:
13+
- Package.json dependencies and their purposes
14+
- Framework and library versions
15+
- Database schema and ORM usage
16+
- Build tools and development workflow
17+
- Deployment and infrastructure setup
18+
- Code organization and architecture patterns
19+
- Testing frameworks and quality tools
20+
- CI/CD and development processes
21+
3. **Ask Clarifying Questions:** Before writing the document, ask 4-6 targeted questions based on the technical analysis. Focus on deployment, hosting, development workflow, and technical decisions. Provide lettered/numbered options for easy response.
22+
4. **Generate Documentation:** Create a comprehensive tech stack document using the structure outlined below.
23+
5. **Save Documentation:** Save as `tech-stack.md` in the `.taskmaster/docs/` directory.
24+
25+
## Clarifying Questions (Examples)
26+
27+
Adapt these questions based on the technical analysis:
28+
29+
- **Hosting & Deployment:** "Where is this application deployed? (e.g., Vercel, AWS, self-hosted)" or "What deployment strategy do you use?"
30+
- **Database & Storage:** "What database are you using and how is it hosted?" or "Do you use any external storage services?"
31+
- **Development Workflow:** "What's your preferred development workflow? (e.g., feature branches, trunk-based development)"
32+
- **Environment Management:** "How do you handle different environments (dev, staging, prod)?"
33+
- **Performance & Monitoring:** "What tools do you use for monitoring, logging, or error tracking?"
34+
- **Team Collaboration:** "What tools does your team use for collaboration and project management?"
35+
- **Quality Assurance:** "What's your testing strategy and what tools do you use for code quality?"
36+
- **Third-Party Services:** "What external APIs or services does your application integrate with?"
37+
38+
## Document Structure
39+
40+
The generated document must follow this technical structure:
41+
42+
### **Overview**
43+
44+
- Brief description of the application's technical nature
45+
- Technology stack summary
46+
- Architecture approach (monolith, microservices, etc.)
47+
48+
### **Programming Language & Runtime**
49+
50+
- Primary programming language and version
51+
- Runtime environment and version
52+
- Type system and language features used
53+
54+
### **Frontend**
55+
56+
- UI Framework/Library and version
57+
- Styling approach and frameworks
58+
- Component libraries and design systems
59+
- State management solutions
60+
- Build tools and bundlers
61+
- Browser support and compatibility
62+
63+
### **Backend**
64+
65+
- Backend framework and architecture
66+
- API design (REST, GraphQL, tRPC, etc.)
67+
- Authentication and authorization
68+
- Middleware and security
69+
- File handling and uploads
70+
71+
### **Database & Storage**
72+
73+
- Database type and version
74+
- ORM/Query builder
75+
- Schema management and migrations
76+
- Caching solutions
77+
- File storage solutions
78+
- Data backup and recovery
79+
80+
### **Development Tools & Workflow**
81+
82+
- Package manager
83+
- Code formatting and linting
84+
- Type checking and compilation
85+
- Testing frameworks and strategies
86+
- Development server and hot reload
87+
- Version control workflow
88+
89+
### **Deployment & Infrastructure**
90+
91+
- Hosting platform and services
92+
- Build and deployment pipeline
93+
- Environment configuration
94+
- Domain and DNS management
95+
- SSL/TLS and security
96+
- Monitoring and logging
97+
98+
### **External Integrations**
99+
100+
- Third-party APIs and services
101+
- Payment processing
102+
- Email services
103+
- Analytics and tracking
104+
- Error monitoring
105+
- Performance monitoring
106+
107+
### **Quality Assurance & Testing**
108+
109+
- Testing strategy and frameworks
110+
- Code coverage tools
111+
- End-to-end testing
112+
- Performance testing
113+
- Security testing
114+
- Code review process
115+
116+
### **Project Structure**
117+
118+
- Folder organization and conventions
119+
- Module system and imports
120+
- Configuration files
121+
- Environment variables
122+
- Build artifacts and outputs
123+
124+
### **Schemas & Data Models**
125+
126+
- Database schema (if applicable)
127+
- API schemas and validation
128+
- Type definitions and interfaces
129+
- Data relationships and constraints
130+
131+
## Target Audience
132+
133+
The document should serve:
134+
135+
- **Developers** joining the project who need technical onboarding
136+
- **DevOps engineers** setting up infrastructure and deployment
137+
- **Technical architects** evaluating or improving the tech stack
138+
- **Security teams** understanding the technical landscape
139+
- **Future maintainers** who need to understand technical decisions
140+
141+
The language should be technical, precise, and include specific version numbers and configuration details.
142+
143+
## Key Principles
144+
145+
1. **Technical Specificity:** Include exact versions, configuration details, and implementation specifics
146+
2. **Completeness:** Cover all major technical components and dependencies
147+
3. **Developer-Focused:** Emphasize how technologies are used and why they were chosen
148+
4. **Actionable:** Provide enough detail for setup, development, and deployment
149+
5. **Current:** Reflect the actual current state of the codebase
150+
151+
## Output
152+
153+
- **Format:** Markdown (`.md`)
154+
- **Location:** `.taskmaster/docs/`
155+
- **Filename:** `tech-stack.md`
156+
157+
## Final Instructions
158+
159+
1. Do NOT start implementing the document immediately
160+
2. First analyze the codebase thoroughly, examining package.json, config files, and code structure
161+
3. Ask clarifying questions with lettered/numbered options for easy selection
162+
4. Generate a complete technical document following the structure above
163+
5. Include specific versions, configuration examples, and technical details
164+
6. Focus on HOW things are implemented, complementing the high-level app-design-document
165+
7. After saving, suggest creating a complementary app-design-document if one doesn't exist

‎templates/plate-template/.claude/commands/debug.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
1. Reflect on 5-7 different possible sources of the problem
2+
2. Distill those down to 1-2 most likely sources
3+
3. Add additional logs to validate your assumptions and track the transformation of data structures throughout the application control flow before we move onto implementing the actual code fix
4+
4. Use the "getConsoleLogs", "getConsoleErrors", "getNetworkLogs" & "getNetworkErrors" tools to obtain any newly added web browser logs
5+
5. Obtain the server logs as well if accessible - otherwise, ask me to copy/paste them into the chat
6+
6. Deeply reflect on what could be wrong + produce a comprehensive analysis of the issue
7+
7. Suggest additional logs if the issue persists or if the source is not yet clear
8+
8. Once a fix is implemented, ask for approval to remove the previously added logs

‎templates/plate-template/.claude/commands/done.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
Complete a Task Master task: $ARGUMENTS (default: next)
2+
3+
Steps:
4+
5+
1. Review the current task with `task-master show $ARGUMENTS`
6+
2. Verify all implementation is complete
7+
3. Run any tests related to this task
8+
4. Mark as complete: `task-master set-status --id=$ARGUMENTS --status=done`
9+
5. Show the next available task with `task-master next`

‎templates/plate-template/.claude/commands/next.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
Find the next available Task Master task and show its details.
2+
3+
Steps:
4+
5+
1. Run `task-master next` to get the next task
6+
2. If a task is available, run `task-master show <id>` for full details
7+
3. Provide a summary of what needs to be implemented
8+
4. Suggest the first implementation step

‎templates/plate-template/.claude/commands/parse.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
TODO: short sentence description of what this command does
2+
3+
Steps:
4+
5+
1. Add tag: `task-master add-tag <name> --description="<description>"`
6+
2. CRITICAL:Use tag: `task-master use-tag <name>`
7+
3. Parse PRD: `task-master parse-prd .taskmaster/docs/prd-<name>.md`
8+
4. Suggest using `/next` command to start with the first task

0 commit comments

Comments
 (0)