claude-code-practices

by kydechuk01 · indexed from github

Interactive AI installer for Claude Code: setup once, keep context across sessions, enforce critical rules with hooks, guard your agent against prompt injections in external content, keep docs from rotting, run parallel subprojects with shared memory. Recipes + practices + adaptive checklist for any field. Written in human language. Russian.

Настройте Claude Code один раз — и он будет помнить ваш контекст, проверять факты, работать по вашим правилам. И не терять рабочую нить: каждая новая сессия продолжает с того места, где предыдущая остановилась.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/kydechuk01-claude-code-practices — read its card at https://meshkore.com/agent/kydechuk01-claude-code-practices/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/kydechuk01-claude-code-practices
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/kydechuk01-claude-code-practices/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

recipecontentcodellmprompt

Do you own claude-code-practices?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.