Install
$ agentstack add skill-hlhr202-swe-skills-architect-setup ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Architect Setup
Use this skill to initialize or resume an Architect project setup. Architect is a project-planning workflow that stores durable project context in an architect/ directory. Setup prepares only the product, guidelines, technology stack, style guides, workflow, and index context. After setup, use architect-discuss to explore the first direction; once scope is confirmed, use architect-propose.
Core Rules
- Follow the bundled resource
references/setup-protocol.mdas the source of truth for the setup sequence. - Use Architect semantics consistently:
architect/,/architect-*,Architect methodology, andarchitect(...)commit scopes. - Use relative paths rooted in the user's project when creating Architect files. Architect-managed files must stay under
architect/; do not use absolute paths or... - Ask the user through the active agent runtime's user-interaction mechanism. If structured choices are unavailable, present the options in text and wait for the user's reply.
- Present detailed Markdown, drafts, diffs, reports, or risk analysis in a normal assistant message before asking for a decision. Use interactive prompts only for concise plain-text questions and short plain-text choices.
- Use the active agent runtime's safest reviewable file-editing mechanism, preferably patch-based, for manual file creation and edits. Do not use shell redirection to write files.
- Validate each operation result before continuing. If a step fails, correct it once when the error is clear; otherwise stop and report the blocker.
- Do not commit unless the user explicitly asks for a commit in the current conversation.
Bundled Templates
- Bundled resource
references/workflow.mdis the default Architect workflow template. - Bundled resources under
references/code_styleguides/*.mdare code style guides. Enumerate this bundled resource directory at setup time so newly added guides are automatically available.
Execution
- Read the bundled resource
references/setup-protocol.md. - Audit the target project for existing
architect/artifacts. - Resume from the correct setup stage or initialize from scratch.
- Stop after core context is complete; do not create or modify proposal or track artifacts.
- Summarize created files and recommend
/architect-discussas the next step.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hlhr202
- Source: hlhr202/swe-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.