Skip to content
Prompt

moleculer-typescript-template — Copilot Instructions

by jellydn

AI Summary

Copilot instructions for a Moleculer TypeScript microservices project that establishes backlog management conventions and task definition standards. Developers working with Moleculer-based microservices benefit from consistent task structuring and decision tracking.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "moleculer-typescript-template — Copilot Instructions" prompt rules to my project.
Repository: https://github.com/jellydn/moleculer-typescript-template

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

This is a Moleculer-based microservices project

Additional task requirements

• Tasks must be atomic and testable. If a task is too large, break it down into smaller subtasks. Each task should represent a single unit of work that can be completed in a single PR. • Never reference tasks that are to be done in the future or that are not yet created. You can only reference previous tasks (id < current task id). • When creating multiple tasks, ensure they are independent and they do not depend on future tasks. Example of wrong tasks splitting: task 1: "Add API endpoint for user data", task 2: "Define the user model and DB schema". Example of correct tasks splitting: task 1: "Add system for handling API requests", task 2: "Add user model and DB schema", task 3: "Add API endpoint for user data".

1. Source of Truth

• Tasks live under backlog/tasks/ (drafts under backlog/drafts/). • Every implementation decision starts with reading the corresponding Markdown task file. • Project documentation is in backlog/docs/. • Project decisions are in backlog/decisions/.

**Title**

Use a clear brief title that summarizes the task.

**Description**: (The **"why"**)

Provide a concise summary of the task purpose and its goal. Do not add implementation details here. It should explain the purpose and context of the task. Code snippets should be avoided.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 1mo ago
Active
AdoptionUnder 100 stars
17 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Stars17
Forks4
Issues14
Updated1mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more