# Layerkit Design Flow

> Decide the simplest client-owned integration shape from code and vendor evidence; prefer updating existing mappers/adapters.

- **Type:** Skill
- **Install:** `agentstack add skill-hariharapanigrahy-layerkit-layerkit-design-flow`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [hariharapanigrahy](https://agentstack.voostack.com/s/hariharapanigrahy)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [hariharapanigrahy](https://github.com/hariharapanigrahy)
- **Source:** https://github.com/hariharapanigrahy/layerkit/tree/main/skills/layerkit-design-flow

## Install

```sh
agentstack add skill-hariharapanigrahy-layerkit-layerkit-design-flow
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# layerkit-design-flow

Use this skill to decide how the client package should express a vendor integration change.

## Protocol

1. Read the existing integration topology: mappers, adapters, routers, registries, tests, and feature flags.
2. Read vendor evidence for the changed endpoint, payload, auth, batching, or ordering requirement.
3. Prefer changing the existing mapper/adapter path.
4. Use a multi-step flow in client code only when vendor evidence requires sequencing, branching, batching, or retries that are not already represented.
5. Before adding a new abstraction, document why the existing abstraction cannot be changed.
6. Update tests around the actual production path.

## Design Outputs

- Existing file/function to update.
- Stale code/docs/tests to delete or rewrite.
- Required source edits.
- Tests to add or update.
- Residual TODOs where the client datalayer cannot satisfy the vendor contract.

## Multi-vendor / new vendor on existing path

When the package already ships one or more vendors and the user wants a **new** vendor:

1. Pick a **sibling vendor** adapter/mapper as the structural reference (`file://` path).
2. Design the new integration by **following that existing path**: same module root, registry/router wire, privacy hooks, and test layout.
3. Prefer cloning the sibling structure over inventing a parallel facade or side registry.
4. Document: sibling reference path → new vendor files → registry entry → tests cloned from sibling.
5. Only introduce a new abstraction when no sibling file can own the vendor-specific behavior, and list what existing surface cannot be extended.

## Forbidden

- Designing a Layerkit runtime flow instead of client-owned source code.
- Adding a side registry/facade when the existing route/mapper can be edited.
- Inventing auth, endpoint, batching, or routing behavior without evidence.
- Finalizing while package verification fails.
- Designing a freestyle tree beside an existing multi-vendor module root.

## Success Criteria

- [ ] The chosen shape is grounded in existing client code.
- [ ] The smallest viable source edit is identified.
- [ ] New abstractions are justified by concrete existing-code limits.
- [ ] Verification path is clear before source edit begins.
- [ ] New-vendor designs name the sibling path they follow (or residual why none exists).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [hariharapanigrahy](https://github.com/hariharapanigrahy)
- **Source:** [hariharapanigrahy/layerkit](https://github.com/hariharapanigrahy/layerkit)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-hariharapanigrahy-layerkit-layerkit-design-flow
- Seller: https://agentstack.voostack.com/s/hariharapanigrahy
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.