wize-technical-research Cursor ruleA
wize-technical-research from qwize-br/wize-development-kit is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add qwize-br/wize-development-kit/.cursor/rules/wize-technical-research.mdc@git:20261019.207e46cPins git:20261019.207e46c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- qwize-br/wize-development-kit
- Path
.cursor/rules/wize-technical-research.mdc- Versions recorded
- 2
- Latest version
- git:20261019.207e46c, committed Oct 19, 2026
- First version recorded
- Jun 13, 2026
- Size
- 1,764 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use quando precisar pesquisar tecnologias, stacks, bibliotecas ou decisões técnicas.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Technical Research
> **Variante de pesquisa.** Para outros tipos de pesquisa, veja:
> - Mercado/concorrência → `/wize-market-research`
> - Domínio/indústria → `/wize-domain-research`
> - Técnica/stack → `/wize-technical-research`
> - Pesquisa geral (dispatcher) → `/wize-research`
# Technical Research
**Goal.** Conduct technical research on technologies, tools, and architecture patterns to inform stack decisions.
Pepper Potts drives. Tony Stark consumes the output directly. Peggy Carter edits prose.
Output lands in `.wize/planning/research/technical-{slug}-research-{date}.md`.
## When to use
- "Should we use X or Y?"
- "What is the current state of Z technology?"
- "I need a technical comparison of..."
## Inputs
- Open questions from `.wize/planning/brief.md` or `.wize/planning/tech-vision.md`
- User-provided technology or architectural topic
- Web search access
## Outputs
- `.wize/planning/research/technical-{slug}-research-{date}.md`
## Workflow architecture
Step-file architecture with six steps:
1. Scope confirmation
2. Technical overview
3. Integration patterns
4. Architectural patterns
5. Implementation research
6. Research synthesis
## On activation
…Read the whole file at its exact version.
How to install
mdr add qwize-br/wize-development-kit/.cursor/rules/wize-technical-research.mdc@sha256:10c48016e75ad052The line at the top of this page pins the label git:20261019.207e46c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ft4ctrb47qcz3hbr)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 13, 2026 and Oct 19, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.207e46c latest | 2026-10-19 | 207e46c | 1,764 B | A | view · diff |
| git:20260613.7bd4681 | 2026-06-13 | 7bd4681 | 1,433 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1764 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qwize-br/wize-development-kit · 19 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ft4ctrb47qcz3hbr GET https://markdownregistry.com/api/v1/resolve?ref=qwize-br/wize-development-kit/.cursor/rules/wize-technical-research.mdc GET https://markdownregistry.com/api/v1/blob/10c48016e75ad052fdbe49b2b19c2b0971befc677b9d0e29630f1589a57300d2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.
More from qwize-br/wize-development-kit
Every file in qwize-br/wize-development-kit