SuperAPI AI Directory

aisdlc-project-discover-level0-memory

General & other

View repository

Updated 10-16 08:50

About this skill

aisdlc-project-discover-level0-memory(Step2:Level-0 / Memory)

Overview

The goal of Memory is "3-minute onboarding": what the project is, what the boundaries are, how to run it, how to verify it, and where the authoritative entry points are.

Writing constraints: short, only write stable entry points and boundaries, use evidence links.

Announce at the start:"I am using the aisdlc-project-discover-level0-memory skill to generate project-level Memory (structure/tech/product/glossary)."

Output files (fixed 4 files)

  • .aisdlc/project/memory/structure.md
  • .aisdlc/project/memory/tech.md
  • .aisdlc/project/memory/product.md
  • .aisdlc/project/memory/glossary.md

Minimal template (copyable)

memory/structure.md

  • Project form: monolith/multi-service/Monorepo (writeEvidence entry point: directory/script/CI)
  • Entry points (must be locatable):
    • Local startup:<命令或脚本路径>
    • Testing:<命令或脚本路径>
    • Build/release:<CI job 配置路径 或 脚本>
  • Map entry points:
    • Component index:../components/index.md
    • Contract index:../contracts/index.md
    • Runtime entry:../ops/(if any)
  • ## 证据入口清单(临时)(draft from Step0, later split and filled in)

memory/tech.md

  • Tech stack (list only stable choices): language/framework/database/messaging/gateway
  • Engineering guardrail entry points: lint/test/security scan (commands and CI job configuration locations)
  • NFR guardrail entry points: performance/availability/cost/security (link to ../nfr.md or external specifications)

memory/product.md

  • Business boundaries: In/Out (one sentence + evidence entry point link)
  • Key business module entry points:../products/index.md(if any)
  • Key terminology entry points:./glossary.md

memory/glossary.md

  • Term: definition (1 sentence) + authoritative source link (contract page/code type/ADR/external documentation)

Common mistakes

  • Writing Memory as a "project manual": Memory only does entry points and boundaries; details should link to module pages/contract pages/ops.
  • Making things up to look complete: if there is no evidence, write "not found + how to find it next", do not guess.

Red flag checklist (if any one appears: stop and correct)

  • Memory contains field-level constraints, detailed timing, migration steps, or a full operations manual
  • "First write a long overview, add entry links later" (entry points are the core of Memory)
  • Terminology has no authoritative source link (it becomes an oral definition and drifts quickly)