Develop the go-lcpd daemon/tools (Go). Follow repo principles (robustness, TDD, lint) and validate with make test/lint/gen.
Scanned 2/12/2026
Install via CLI
Skills Directoryopenskills install majiayu000/claude-skill-registry---
name: lcp-go-lcpd
description: Develop the go-lcpd daemon/tools (Go). Follow repo principles (robustness, TDD, lint) and validate with make test/lint/gen.
metadata:
short-description: Work on the go-lcpd implementation
---
You are working in the `go-lcpd/` module (the reference LCP daemon and tools).
## Scope
- Module: `go-lcpd/`
- Primary behavior sources:
- Protocol spec: `docs/protocol/protocol.md`
- WYSIWID design doc (when present): `go-lcpd/spec.md` (see `$lcp-wysiwid-spec`)
## Development principles
These are the consolidated rules that previously lived in `go-lcpd/AGENTS.md`:
1. If `go-lcpd/spec.md` exists, implementation MUST match the behavior defined there.
2. Design for robustness. Keep modules aligned with SRP.
3. Use a ubiquitous language. Keep terminology consistent across code and docs.
4. Test-first. Prefer TDD when changing behavior.
5. Run golangci-lint v2. When changing code, run `make lint` and fix findings.
6. Use `cmp.Diff` in tests. Compare expected vs actual with `github.com/google/go-cmp/cmp.Diff`.
7. Make logging diagnosable. Logging level MUST be configurable (for example via env vars).
8. Prefer lnd libraries. Use lnd-provided APIs/libraries before re-implementing.
## Go documentation and commenting (house style)
- Every function should have a comment describing purpose and assumptions.
- Function comments start with the function name (Effective Go), use complete sentences.
- Comments in code should explain intent, not restate the obvious.
## Workflow
1. Locate the relevant codepath under `go-lcpd/internal/` or `go-lcpd/tools/`.
2. If changing protobufs, edit the `.proto` sources and regenerate instead of hand-editing generated code.
3. Prefer small, testable changes; add/update unit tests and integration tests as needed.
4. If you are authoring/changing `go-lcpd/spec.md`, use `$lcp-wysiwid-spec`.
## Validation (run from `go-lcpd/`)
- `make gen` (only if protobuf / generated code changes)
- `make test`
- `make lint`
- `make fmt`
Optional integration test (regtest):
- `LCP_ITEST_REGTEST=1 go test ./itest/e2e -run Regtest_LNDPayment -count=1 -v`
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
