impactjo/home-memory/home-memory-documentation

Document with Home Memory

Help the user produce retrievable, evidence-based documentation at the detail their task needs.

Use the documentation reference

Read the relevant sections of the documentation model before making the documentation decision:

• Sections 1.1 to 1.3 for locations, components, physical runs, categories, and statuses.
• Sections 2.1 to 2.4 for record boundaries, examples, and refining existing documentation.
• Sections 3.1 to 3.3 for information placement; section 4 for explaining a decision to the user.
• Section 3.4 for concrete questions about organizing document and image files or relating their contents to documented objects.

Apply the principles and Home Memory field mapping from that reference. Read only the sections needed for the current decision.

Apply it to the task

• Identify the unresolved decision and the facts already supplied. For live documentation, inspect only the relevant existing records and relationships through HomeMemoryMCP before proposing additions. Reuse identities and follow established project naming conventions when naming new records.
• Create a separate record when independent treatment provides concrete retrieval, relationship, maintenance or history value. Product identity, category, location and lifecycle are signals to consider, not sufficient conditions.
• Store information in the most specific authoritative place available. Use HM's field mapping; consider any existing type information exposed by the MCP as read-only context instead of duplicating it. Do not invent a type-management workflow.
• Keep unknown facts unresolved. Ask only when missing information changes the representation or prevents the requested action; continue independent parts where possible. Do not ask for optional details or suggest measurement, research or follow-up work solely because the data model provides a field. Additional collection effort requires concrete value for the current task or a stated later use. Do not routinely present omitted optional values as documentation gaps, warnings or follow-up tasks. When the missing fact determines the target of an assignment, ask a direct clarification question and wait for the answer before assigning it. Merely stating that the target remains to be clarified is not enough. Do not turn a reference example into a required structure or a local convention into a universal rule.
• When writing through the product MCP, pass intended characters literally. Do not pre-encode text as HTML/XML entities; an entity sequence should remain literal only when it is itself the intended content.
• Explain or propose when asked for advice. When asked to record information, carry out the authorized changes using the available tool contracts and check the resulting records. The skill does not expand the task into a general cleanup.

HomeMemoryMCP is required for inspecting or changing the live documentation. If it is unavailable, use supplied information for advice and identify what could not be checked or saved. Conceptual explanations do not require a connection or a preliminary tool call.

Respond in the user's language, using concise, natural terms instead of internal field keys, parameter names or tool names. Prefer known product labels; otherwise translate a clear field meaning naturally. Keep exact internal interface identifiers in tool calls and mention them to the user only when explicitly requested or needed for troubleshooting. State the decision or completed change and any material unresolved information; avoid a full field tour for a small task.