signal-capture
Detect and capture technical preferences, naming conventions, and architectural practices from user messages into Packmind standards. Trigge
Open source Repository Open in the app JSON README (API)
About
Detect and capture technical preferences, naming conventions, and architectural practices from user messages into Packmind standards. Trigger when user prescribes HOW to code rather than WHAT to build
Details
- Kind
- Agent skills
- Topic
- No topic detected
- Publisher
- packmindhub
- Origin
- majiayu
- Category
- ferramentas
- Stars
- 150
- Forks
- 17
- Open pull requests
- 28
- Last push
- 2026-09-04T15:22:01Z
- Repository state
- ativo
- Language
- TypeScript
- License
- Apache-2.0
- Added
- 2026-09-01 17:10:37
- Updated
- 2026-09-01 17:10:37
- Origin id
packmindhub/packmind/.claude/skills/signal-capture@main
README
# One Engineering Playbook. Synced Everywhere. For Every AI Coding Agent.   [](https://github.com/PackmindHub/packmind/actions/workflows/main-oss.yml)    **❗ The 2 big problems every AI-native engineer runs into** ### **1️⃣ “What do I even put in these AI instructions?”** Every tool expects its own inputs: - **Copilot** → `.github/copilot-instructions.md`, chat modes, reusable prompts - **Claude** → `CLAUDE.md`, commands, skills - **Cursor** → `.cursor/rules/*.mdc`, commands, skills - **AGENTS.md** → `AGENTS.md` - _(with more formats appearing every month…)_ But your team’s **actual standards aren’t stored anywhere**: - architecture rules → buried in Slack or Notion - naming conventions → stuck in your head - patterns → hiding in PR comments - best practices → scattered across repos 👉 **Packmind helps you turn all of this into a real engineering playbook** (standards, commands, skills) so **AI agents finally code _your way_.** ### **2️⃣ “Why am I copy-pasting this across every repo and every agent?”** Every repo. Every assistant. Different files, different folders, different formats. Keeping everything in sync is impossible. 👉 **Packmind centralizes your playbook once — and distributes it everywhere**, generating the exact instruction files each AI tool needs, optimized for context. --- ## 🆚 Why Packmind over a plain Claude Code marketplace or a plain centralized Git repository? A marketplace distributes skills and commands from a Git repo. Packmind does more: - **Controlled editing:** context files go through a clear ownership and approval workflow. No PR discipline or CODEOWNERS conventions to enforce. - **Simplified updates:** update proposals are submitted from the project codebase, no separate repo to clone or PR. - **Multi-agent:** one source, rendered for Claude Code, Copilot, Cursor and more. No parallel CLAUDE.md or .cursor/rules to maintain. - **Adoption tracking:** see which context files are used, in which repo, at which version. A marketplace ships content. Packmind governs it. --- # Get started Choose your preferred setup option: - **Cloud version**: Get started at [https://app.packmind.ai](https://app.packmind.ai/sign-up?utm_source=oss) (free account) - **Self-hosted**: Deploy on your own infrastructure using [Docker Compose or Kubernetes](https://docs.packmind.com/getting-started/gs-install-self-hosted) ## Option 1: Install the CLI (recommended) Follow the instructions during the onboarding to connect to your Packmind organization You can find them at anytime in the **Settings** menu. Once authenticated, run in your project: ```bash $> packmind init ``` Then, in your favorite ai coding agent, run: ``` /packmind-onboard ``` To create your first standards and commands from your codebase. # Documentation Available here: [https://docs.packmind.com](https://docs.packmind.com). # :compass: Key Links - [**Docs →**](https://docs.packmind.com) - [**Packmind Cloud →**](https://app.packmind.ai/sign-up) - [**Join the Slack Community →**](https://join.slack.com/t/promyze/shared_invite/zt-vf6asxsj-aH1RbzuoOR5DNFexeaATVQ)