A pre-submission checklist for a documentation project. It checks document metadata, Markdown formatting, bold-text rendering, internal links, indexes, and whether code examples need compilation checks.
Update both the README.md and CLAUDE.md files as appropriate. If either file does not exist, please create it. Generate the CLAUDE.md file as though the user invoked the init task.
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.
A clarification command that asks up to five focused questions about an unfinished feature specification. A feature specification is the written description of what a software change should do.
:::info This document covers all build, test, and smoke commands for eIsland native plugins. Windows plugins live under plugins/windows/; macOS helpers live under plugins/macos/. Each plugin has its own package.json with independent scripts. ::.
A planning command that restates a development request, identifies risks, and creates a step-by-step implementation plan. It waits for the user's approval before code changes begin.
Defines the slayer command line's user-facing contract: how errors are reported, the version and debug flags, the search and sample-refresh command shapes, and how query results print as a table.
Markdown files that create reusable /slash-commands. Commands have been merged into skills, but existing command files still work and this directory is still supported.
The invocable command plugins live here: leaf plugins whose body is a prompt preset a human can pick from the / dropdown while launching or driving a session, each carrying surface: command. Grouping them keeps .plugins/ legible at a glance — the command presets on this shelf, the skill plugins on [[skills]], the…
Review factory performance and propose deliberate constraint changes - tighten where a gate let something through, loosen where a class of change has been green long enough.
Implement a standardized repository with soft delete functionality and comprehensive tests to ensure maintainable code and reliable data access patterns in the Packmind codebase.
Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently? Or is there other places that we can refactor and revisit things before pushing this pr?
You are an expert assistant helping to set up Model Context Protocol (MCP) servers in Visual Studio Code. Your task is to help create and configure a .vscode/mcp.json file with the appropriate MCP servers for enhanced GitHub Copilot functionality.
This command is designed to create a comprehensive Product Requirement Prompt (PRP) for building Model Context Protocol (MCP) servers referencing this codebase patterns mirroring tool setups for the users specific requirements.
★not rated 302 1y agoA46 tokens
copy · 86%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: