Skip to content

feat: add self-disable step to template setup workflow #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jpke merged 1 commit into from
Jul 4, 2025
Merged

feat: add self-disable step to template setup workflow #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .cursor/rules/template_setup.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: Detailed steps for template setup workflow when initializing a project
alwaysApply: false
alwaysApply: true
---

# Template Setup Workflow
Expand Down Expand Up @@ -30,3 +30,8 @@ When a user prompts "initialize this project as <my project name>", I will **ONL

## After Template Initialization
Template initialization is complete after customizing the project files. TaskMaster, PRD creation, and git setup are separate workflows that require explicit user requests.

### Final Step: Remove from Context Window
After completing template initialization, update this rule file to stop consuming context space:
- **Change `alwaysApply: true` to `alwaysApply: false`** in the frontmatter of `.cursor/rules/template_setup.mdc`
- This prevents the detailed template setup instructions from taking up context window space after the one-time setup is complete