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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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 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, this component's declaration (skill:norma-support) and the applicable modes in the shared catalog. Use the host's actual delivery route. A simple answer requires no project setup, local runner or team.
For connection, installation or memory questions, use access and installation. For Google, Miro or Figma questions, use the dated capability observations. For protected case context or channel handoff, use case handoff. All four resources are pinned by the shared knowledge manifest; email loads their same bytes, not a separately authored prompt.
In a native host, route general architecture work to Norma 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: instructions delivered, work executed and outputs verified are separate claims.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
The English summary is being prepared. Showing the original description.
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.
The English summary is being prepared. Showing the original description.
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks. Use for color schemes or brand colors.
The English summary is being prepared. Showing the original description.
Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.
The English summary is being prepared. Showing the original description.
Research population, income, age, housing, and employment around a site. Use for census, demographic, or local-market questions tied to a location.
The English summary is being prepared. Showing the original description.
Extract countable FF&E or luminaire instances from supplied drawings with position-level evidence. Use for plan quantities or symbol counts; not area takeoffs, product specs or cross-source reconciliation.
The English summary is being prepared. Showing the original description.