95c299df64
* move claude rules and commands to assets/claude * update claude profile to copy assets/claude to .claude * fix formatting * feat(profiles): Implement unified profile system - Convert Claude and Codex profiles to use createProfile() factory - Remove simple vs complex profile distinction in rule transformer - Unify convertAllRulesToProfileRules() to handle all profiles consistently - Fix mcpConfigPath construction in base-profile.js for null mcpConfigName - Update terminology from 'simpleProfiles' to 'assetOnlyProfiles' throughout - Ensure Claude .claude directory copying works in both CLI and MCP contexts - All profiles now follow same execution flow with proper lifecycle functions Changes: - src/profiles/claude.js: Convert to createProfile() factory pattern - src/profiles/codex.js: Convert to createProfile() factory pattern - src/utils/rule-transformer.js: Unified profile handling logic - src/utils/profiles.js: Remove simple profile categorization - src/profiles/base-profile.js: Fix mcpConfigPath construction - scripts/modules/commands.js: Update variable naming - tests/: Update all tests for unified system and terminology Fixes Claude profile asset copying issue in MCP context. All tests passing (617 passed, 11 skipped). * re-checkin claude files * fix formatting * chore: clean up test Claude rules files * chore: add changeset for unified profile system * add claude files back * add changeset * restore proper gitignore * remove claude agents file from root * remove incorrect doc * simplify profiles and update tests * update changeset * update changeset * remove profile specific code * streamline profiles with defaults and update tests * update changeset * add newline at end of gitignore * restore changes * streamline profiles with defaults; update tests and add vscode test * update rule profile tests * update wording for clearer profile management * refactor and clarify terminology * use original projectRoot var name * revert param desc * use updated claude assets from neno * add "YOUR_" before api key here * streamline codex profile * add gemini profile * update gemini profile * update tests * relocate function * update rules interactive setup Gemini desc * remove duplicative code * add comma
2.7 KiB
2.7 KiB
Learn about Task Master capabilities through interactive exploration.
Arguments: $ARGUMENTS
Interactive Task Master Learning
Based on your input, I'll help you discover capabilities:
1. What are you trying to do?
If $ARGUMENTS contains:
- "start" / "begin" → Show project initialization workflows
- "manage" / "organize" → Show task management commands
- "automate" / "auto" → Show automation workflows
- "analyze" / "report" → Show analysis tools
- "fix" / "problem" → Show troubleshooting commands
- "fast" / "quick" → Show efficiency shortcuts
2. Intelligent Suggestions
Based on your project state:
No tasks yet?
You'll want to start with:
1. /project:task-master:init <prd-file>
→ Creates tasks from requirements
2. /project:task-master:parse-prd <file>
→ Alternative task generation
Try: /project:task-master:init demo-prd.md
Have tasks? Let me analyze what you might need...
- Many pending tasks? → Learn sprint planning
- Complex tasks? → Learn task expansion
- Daily work? → Learn workflow automation
3. Command Discovery
By Category:
- 📋 Task Management: list, show, add, update, complete
- 🔄 Workflows: auto-implement, sprint-plan, daily-standup
- 🛠️ Utilities: check-health, complexity-report, sync-memory
- 🔍 Analysis: validate-deps, show dependencies
By Scenario:
- "I want to see what to work on" →
/project:task-master:next - "I need to break this down" →
/project:task-master:expand <id> - "Show me everything" →
/project:task-master:status - "Just do it for me" →
/project:workflows:auto-implement
4. Power User Patterns
Command Chaining:
/project:task-master:next
/project:task-master:start <id>
/project:workflows:auto-implement
Smart Filters:
/project:task-master:list pending high
/project:task-master:list blocked
/project:task-master:list 1-5 tree
Automation:
/project:workflows:pipeline init → expand-all → sprint-plan
5. Learning Path
Based on your experience level:
Beginner Path:
- init → Create project
- status → Understand state
- next → Find work
- complete → Finish task
Intermediate Path:
- expand → Break down complex tasks
- sprint-plan → Organize work
- complexity-report → Understand difficulty
- validate-deps → Ensure consistency
Advanced Path:
- pipeline → Chain operations
- smart-flow → Context-aware automation
- Custom commands → Extend the system
6. Try This Now
Based on what you asked about, try: [Specific command suggestion based on $ARGUMENTS]
Want to learn more about a specific command? Type: /project:help