AlpacaLabsLLC/skills-for-architects / skills/norma-support
norma-support
VerifiedHelp users connect Arch Studio, understand its access and memory, choose a first workflow, and troubleshoot from reported evidence. General architecture and project execution stays with its owning skill.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 808 B |
| SKILL.md | skill md | 2.2 KB |
| host-contract.json | config | 1.0 KB |
| knowledge-manifest.json | config | 785 B |
| references/access-and-installation.md | markdown | 14.2 KB |
| references/capability-observations.md | markdown | 3.5 KB |
| references/case-handoff.md | markdown | 3.3 KB |
| references/conversation-knowledge.md | markdown | 10.0 KB |
SKILL.md
View on GitHub---
name: norma-support
description: "Help users connect Arch Studio, understand its access and memory, choose a first workflow, and troubleshoot from reported evidence. General architecture and project execution stays with its owning skill."
allowed-tools:
- Read
- Glob
- Grep
- AskUserQuestion
---
# Norma support
This MCP workflow is a complete harness-native answer procedure with `operations: []`. Read the applicable knowledge and supplied evidence, answer or prepare the scoped handoff, and report its actual status. It has no hidden executable step. The separate email application retains its own access boundary and deployment identity.
Use the [shared conversational knowledge](references/conversation-knowledge.md) for every support conversation. It is the same canonical resource loaded by the separately deployed email service. Loading this skill does not create that service, a case, a connection or authority to send a message.
Read the [host contract](../../docs/host-harness-contract.md), this component's [declaration](host-contract.json) (`skill:norma-support`) and the applicable modes in the [shared catalog](../../corpus/host-contracts.json). Use the host's actual [delivery route](../../docs/host-adapters.md). A simple answer requires no project setup, local runner or team.
For connection, installation or memory questions, use [access and installation](references/access-and-installation.md). For Google, Miro or Figma questions, use the dated [capability observations](references/capability-observations.md). For protected case context or channel handoff, use [case handoff](references/case-handoff.md). All four resources are pinned by [the shared knowledge manifest](knowledge-manifest.json); email loads their same bytes, not a separately authored prompt.
In a native host, route general architecture work to [Norma](../norma/SKILL.md) or its domain owner under the user's existing authorization. This support entry point explains and guides; it does not inspect attachments, execute diagnostics, edit files or perform project production. Follow the [completion contract](../../docs/completion-reporting.md): instructions delivered, work executed and outputs verified are separate claims.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |