All authors

Claude Skills by talayash
github.com/talayash18 skills0 installs46 views
- Claude TerminalDevelopment conventions and patterns for Agentrium (formerly claude-terminal). TypeScript Vite project with freeform commits.Votes: 0GitHub stars: 42
- Frontend PatternsReact/TypeScript/xterm.js patterns for Agentrium frontendVotes: 0GitHub stars: 42
- Local QaHow to run Agentrium locally for QA/manual verification alongside the user's running production client. Use whenever asked to run, start, launch, QA, smoke-test, or screenshot the desktop app. Contains the hard rule about never touching the running production instance or port 5173.Votes: 0GitHub stars: 42
- Rust PatternsRust/Tauri patterns and best practices for Agentrium backendVotes: 0GitHub stars: 42
- Security ReviewSecurity audit checklist and patterns for Tauri desktop apps with PTY spawningVotes: 0GitHub stars: 42
- Tdd WorkflowTest-Driven Development workflow with RED-GREEN-REFACTOR cycle and git checkpointsVotes: 0GitHub stars: 42
- Verification LoopFull build/type/lint/security verification pipeline for AgentriumVotes: 0GitHub stars: 42
- Debugging Runtime LogsUse when debugging a runtime failure in a locally-running fleet of Spring Boot microservices - correlates logs across services by a trace key, reconstructs the cross-service timeline, isolates the failing hop, and maps it back to source.Votes: 0GitHub stars: 2
- Federating Mcp ServersUse when a fleet service ships its own Spring AI MCP server - explains how to discover those servers from the spring-fleet config and federate them alongside the spring-fleet MCP tools so the agent has one unified tool surface across the fleet.Votes: 0GitHub stars: 2
- Spring Fleet Logging SetupUse when fleet logs are console-only or scattered and cross-service correlation needs a stable location - installs a logback convention so every service writes <logDir>/<service>.log with OTel trace_id / span_id and legacy sessionId / requestId in the pattern.Votes: 0GitHub stars: 2
- Tracing Across ServicesUse when you need to understand how a request, endpoint, or feature flows across multiple Spring Boot service repos and shared libraries - produces an ordered call chain with file:line citations, following inter-service proxy-lib calls.Votes: 0GitHub stars: 2
- DebugDebug a runtime failure across the fleet by correlating logs on an OTel trace_id / sessionId / requestId, or by reading a pasted Grafana / stack-trace screenshot, and mapping the failure back to source.Votes: 0GitHub stars: 2
- DoctorCheck fleet configuration, repository paths, logs, port conflicts and required executables.Votes: 0GitHub stars: 2
- Fleet InitScan a repos directory and generate (or update) spring-fleet.config.json for the fleet.Votes: 0GitHub stars: 2
- ImpactFind every consumer of a shared-lib symbol, file, or API across the fleet's service repos. Outputs an impact list with file:line citations.Votes: 0GitHub stars: 2
- LogsTail or aggregate logs from the fleet's services: file-based when present, kubectl-based when the config has a k8s block (for mirrord / in-cluster runs).Votes: 0GitHub stars: 2
- RunPlan or launch the fleet locally: compose-first per service, with stdout tee'd to logDir so /debug can read it later.Votes: 0GitHub stars: 2
- TraceTrace how an endpoint or feature flows across the fleet's service repos and shared libraries, with file:line citations.Votes: 0GitHub stars: 2