Nm Archetypes Architecture Paradigm Service Based

Design coarse-grained service architecture for deployment independence without microservices complexity and overhead

Security Scan

This is an instruction-only design guidance skill about service-based architecture; its declared requirements and runtime instructions are coherent with that purpose and it does not request credentials, installs, or privileged access.

Purpose & Capability

The name and description promise coarse-grained service-architecture guidance and the SKILL.md contains exactly that guidance (when to use, adoption steps, risks, deliverables). There are no unrelated environment variables, binaries, or install steps requested.

Instruction Scope

Instructions are high-level architecture and process guidance; they do not tell the agent to read system files, access environment variables, or transmit data to external endpoints. Troubleshooting notes mention generic CLI errors but do not execute or require system-level operations.

Install Mechanism

No install spec and no code files are present (instruction-only), so nothing is written to disk or downloaded by the skill itself.

Credentials

The skill declares no required env vars, credentials, or config paths. There is no disproportionate or unexplained access requested.

Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous invocation allowed. It does not request persistent presence or the ability to modify other skills or system settings.

Assessment

This skill is essentially documentation and safe to enable: it only offers architectural recommendations and does not request secrets, install software, or perform actions. Before acting on its recommendations, remember that implementing them in your environment may require infrastructure changes, database migration strategies, and team governance—those operational activities are outside the skill and may need privileged access. If you later install the full Claude plugin referenced in the SKILL.md (for commands/hooks), review that plugin's permissions and any install scripts separately, as those could request additional access not present in this instruction-only skill.

Night Market Skill — ported from claude-night-market/archetypes. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

The Service-Based Architecture Paradigm

When To Use

• Multi-team organizations with domain-aligned services
• Systems requiring independent deployment of components

When NOT To Use

• Single-team projects small enough for a monolith
• Latency-sensitive systems where inter-service calls are prohibitive

When to Employ This Paradigm

• When teams require a degree of deployment independence but are not yet prepared for the complexity of managing numerous microservices.
• When shared databases or large-scale systems (like ERPs) make full service autonomy unrealistic.
• When establishing clear service contracts for partner teams or external consumers.

Adoption Steps

1. Group Capabilities: Bundle related business functions into a small set of well-defined services, each with a designated owner.
2. Define Service Contracts: Publish formal specifications using standards like OpenAPI or AsyncAPI, including Service Level Agreements (SLAs) and a clear versioning strategy.
3. Control Database Schemas: Even when services share a database, assign explicit ownership for each schema or table. Gate all breaking changes through a formal review process.
4. Establish Service Mediation: Use a service registry or an API gateway to handle routing, authentication, and observability.
5. Plan for Evolution: Identify architectural "hotspots" that are likely candidates for being split into more granular services in the future.

Key Deliverables

• An Architecture Decision Record (ADR) that outlines service boundaries, data ownership rules, and coordination mechanisms.
• A suite of contract tests and consumer-driven contract tests for each service to validate stability.
• Runbooks that describe deployment procedures, rollback plans, and service dependencies.

Risks & Mitigations

• Coupling Through a Shared Database:
  • Mitigation: Changes to a shared database can have cascading effects across services. Mitigate this by using database views, replication, or a formal schema deprecation schedule to manage change.
• Architectural Degradation:
  • Mitigation: Without strong governance, this architecture can degrade into a "distributed monolith"—a monolith with the added complexity of network hops. Track coupling metrics closely and enforce strict ownership of services and data to prevent this.

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag