development
01jpke/cursor-vibe-coding-template
Cursor rule Cursor
Core development practices for frontend, testing, and Python environments.
not rated 16 1y ago A 0 tokens
original MIT
jpke/cursor-vibe-coding-template
Cursor rule Cursor
Standards for accurate, concise, and professional markdown documentation with clear organization and navigation.
not rated 16 1y ago A 0 tokens
original MIT
jpke/cursor-vibe-coding-template
Cursor rule Cursor
Detailed steps for initializing a git repository when cloning the template directly.
not rated 16 1y ago C 12 tokens
original MIT
jpke/cursor-vibe-coding-template
Cursor rule Cursor
Structure and formatting guidelines for Cursor rule files.
not rated 16 1y ago A 0 tokens
original MIT
self_improve
05jpke/cursor-vibe-coding-template
Cursor rule Cursor
Continuously monitor and improve Cursor rules based on emerging code patterns.
not rated 16 1y ago A 377 tokens
copy · 86% MIT
dev_workflow
06jpke/cursor-vibe-coding-template
Cursor rule Cursor
Cursor rule "dev_workflow" from jpke/cursor-vibe-coding-template, covering taskmaster development workflow, the basic loop, standard development workflow process, simple workflow (default starting point) and leveling up: agent-led multi-context workflows.
not rated 16 1y ago A 6,882 tokens
copy · 98% MIT
taskmaster
07jpke/cursor-vibe-coding-template
Cursor rule Cursor
Cursor rule "taskmaster" from jpke/cursor-vibe-coding-template, covering taskmaster tool & command reference, initialization & setup, 1. initialize project (init), 2. parse prd (parseprd) and ai model configuration.
not rated 16 1y ago B 10,998 tokens
copy · 100% MIT
jpke/cursor-vibe-coding-template
Cursor rule Cursor
Detailed steps for template setup workflow when initializing a project.
not rated 16 1y ago A 846 tokens
original MIT
workflow
09jpke/cursor-vibe-coding-template
Cursor rule Cursor
Rules for project workflows including Git, Taskmaster, Memory MCP, and Context7 MCP.
not rated 16 1y ago A 1,178 tokens
original MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: