How do I install the Luthersystems Svc Implement skill?

Run npx skillmds@latest add tomevault-io/luthersystems-svc-implement in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Luthersystems Svc Implement skill do?

Implement It is listed under Coding & Dev Tools on SkillMD.

Is Luthersystems Svc Implement safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Luthersystems Svc Implement?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Luthersystems Svc Implement free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Luthersystems Svc Implement?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Luthersystems Svc Implement by tomevault-io

Name: Luthersystems Svc Implement
Author: tomevault-io

File contents

Implement

Foundation for any code change in luthersystems/svc. Follow this loop for every change.

Workflow

1. Understand the Change

Read CLAUDE.md for project conventions and domain glossary
Read existing code in the target package before modifying
Check if the package has existing tests (*_test.go) to understand testing patterns

2. Create a Feature Branch

# Branch from main, use username/Description format
git checkout main && git pull
git checkout -b sam-at-luther/Short_description

3. Make Changes

Follow existing code style in the package
Add copyright header to new files: // Copyright © <year> Luther Systems, Ltd. All right reserved.
If adding a new package, create it at the top level (flat package structure)
Do NOT edit generated code in oracle/testservice/gen/

4. Format & Lint

# Format
gofmt -w .

# Lint (matches CI — gosec enabled)
golangci-lint run

Fix any lint issues before proceeding. The gosec linter is enabled — pay attention to security findings.

5. Build

go build ./...

6. Test

# Run tests for the changed package
go test -timeout 10m ./your-package/...

# Run the full test suite
go test -timeout 10m ./...

If working on oracle/ tests, the substrate plugin must be available:

# Download the plugin (only needed once)
./scripts/obtain-plugin.sh
# Or via make
make plugin

7. Verify Round-Trip

If your change adds a new public API, verify it with a simple test. If modifying behavior, write a test that captures the expected behavior first (TDD).

Key Reminders

Use testify for assertions in tests (existing pattern in codebase)
The svcerr package maps errors to gRPC status codes — use it for error handling
Context propagation uses grpclogging.AddLogrusField(ctx, key, value) for structured logging
Oracle tests need SUBSTRATEHCP_FILE env var pointing to the plugin binary (set by Makefile)

Checklist

Code builds cleanly (go build ./...)
Lint passes (golangci-lint run)
Tests pass for changed packages
Full test suite passes (go test -timeout 10m ./...)
New files have copyright header
No generated files were manually edited

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: luthersystems-svc-implementdescription: Implement---# ImplementFoundation for any code change in `luthersystems/svc`. Follow this loop for every change.## Workflow### 1. Understand the Change- Read CLAUDE.md for project conventions and domain glossary- Read existing code in the target package before modifying- Check if the package has existing tests (`*_test.go`) to understand testing patterns### 2. Create a Feature Branch```bash# Branch from main, use username/Description formatgit checkout main && git pullgit checkout -b sam-at-luther/Short_description```### 3. Make Changes- Follow existing code style in the package- Add copyright header to new files: `// Copyright © <year> Luther Systems, Ltd. All right reserved.`- If adding a new package, create it at the top level (flat package structure)- Do NOT edit generated code in `oracle/testservice/gen/`### 4. Format & Lint```bash# Formatgofmt -w .# Lint (matches CI — gosec enabled)golangci-lint run```Fix any lint issues before proceeding. The `gosec` linter is enabled — pay attention to security findings.### 5. Build```bashgo build ./...```### 6. Test```bash# Run tests for the changed packagego test -timeout 10m ./your-package/...# Run the full test suitego test -timeout 10m ./...```If working on `oracle/` tests, the substrate plugin must be available:```bash# Download the plugin (only needed once)./scripts/obtain-plugin.sh# Or via makemake plugin```### 7. Verify Round-TripIf your change adds a new public API, verify it with a simple test. If modifying behavior, write a test that captures the expected behavior first (TDD).## Key Reminders- Use `testify` for assertions in tests (existing pattern in codebase)- The `svcerr` package maps errors to gRPC status codes — use it for error handling- Context propagation uses `grpclogging.AddLogrusField(ctx, key, value)` for structured logging- Oracle tests need `SUBSTRATEHCP_FILE` env var pointing to the plugin binary (set by Makefile)## Checklist- [ ] Code builds cleanly (`go build ./...`)- [ ] Lint passes (`golangci-lint run`)- [ ] Tests pass for changed packages- [ ] Full test suite passes (`go test -timeout 10m ./...`)- [ ] New files have copyright header- [ ] No generated files were manually edited---> Converted and distributed by [TomeVault](https://tomevault.io/claim/luthersystems) — claim your Tome and manage your conversions.

Frequently asked questions

Luthersystems Svc Implement