Menü
Store team knowledge, project conventions, and learnings from tasks. Use to remember what works and recall context before new tasks. Connects to Atulya Cloud. (user)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Disciplined development workflow for AI coding agents working in the Atulya monorepo — covers context gathering, branch hygiene, edit/lint/test cycle, API surface changes that require client regen, parallel vs sequential tool use, and the report-back template. Use at the start of any non-trivial Atulya coding task, or when the user asks how to "implement X", "port Y", "change the API", or "ship a feature" in this repo.
Run the Atulya repo through end-to-end system testing — toolchain check, lint, Python pytest, Rust cargo check, TypeScript build, control-plane typecheck, OpenAPI + client regen as a contract test, cross-client field smoke test, and legacy-leak audit. Use when validating a change before commit/PR, after pulling main, before a release, or when the user asks to "run all tests", "verify everything", "system sanity check", or "end-to-end test".
Design a meaningful git commit for the Atulya repo end-to-end — what commands to run to inspect the change, how to decide if it's one commit or several, how to write a message in this repo's `[type] ~ subject` convention with a structured body grouped by surface, and the exact `git add` / heredoc `git commit` invocations to use. Use whenever the user says "commit this", "git commit", "draft a commit message", "what should the commit be", or you've just finished a feature/fix and want to propose a commit before they ask.
Complete Atulya documentation for AI agents. Use this to learn about Atulya architecture, APIs, configuration, and best practices.
Atulya Cortex (TUI/WhatsApp), Hand tools, internet stack (SearXNG/Firecrawl), config, and what-if troubleshooting. Use for cortex wiring, web_search/web_extract, deliberation limits, or docker internet-search compose.
Review changed code against project standards. Checks for missing tests, dead code, type safety, lint issues, and coding conventions. Run after completing any implementation work.
| name | atulya-cloud |
| description | Store team knowledge, project conventions, and learnings from tasks. Use to remember what works and recall context before new tasks. Connects to Atulya Cloud. (user) |
You have persistent memory via Atulya Cloud. This memory bank is shared with the team, so knowledge stored here benefits everyone working on this codebase.
Proactively store team knowledge and recall context to provide better assistance.
Before using memory commands, verify the Atulya CLI is configured:
cat ~/.atulya/config
If the file doesn't exist or is missing credentials, help the user set it up:
Install the CLI (if atulya command not found):
curl -fsSL https://atulya.eightengine.com/get-cli | bash
Create the config file - ask the user for their API Key (get it from https://ui.atulya.eightengine.com):
mkdir -p ~/.atulya
cat > ~/.atulya/config << 'EOF'
api_url = "https://api.atulya.eightengine.com"
api_key = "<user's API key>"
EOF
chmod 600 ~/.atulya/config
Get the bank ID - ask the user for their team's bank ID (e.g., team-myproject)
After setup, use the bank ID in all commands below.
Replace <bank-id> with the user's actual bank ID (e.g., team-frontend).
Use memory retain to store what you learn:
atulya memory retain <bank-id> "Project uses ESLint with Airbnb config and Prettier for formatting"
atulya memory retain <bank-id> "Running tests requires NODE_ENV=test" --context procedures
atulya memory retain <bank-id> "Build failed when using Node 18, works with Node 20" --context learnings
atulya memory retain <bank-id> "Alice prefers verbose commit messages with context" --context preferences
Use memory recall BEFORE starting tasks to get relevant context:
atulya memory recall <bank-id> "project conventions and coding standards"
atulya memory recall <bank-id> "Alice preferences for this project"
atulya memory recall <bank-id> "what issues have we encountered before"
atulya memory recall <bank-id> "how does the auth module work"
Use memory reflect to synthesize context:
atulya memory reflect <bank-id> "How should I approach this task based on past experience?"
This is a shared team bank. Store knowledge that benefits the team. For individual preferences, include the person's name.
Always recall before: