ワンクリックで
cems-foundation
View foundation guidelines (rules, principles, constraints) stored in CEMS memory
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
View foundation guidelines (rules, principles, constraints) stored in CEMS memory
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Search CEMS memory with project-scoped boosting, auto-detecting project from git remote
Search memories for relevant past context, decisions, and patterns
Search memories for relevant past context, decisions, and patterns
Search CEMS long-term memory for relevant past context, decisions, patterns, and preferences
Store memories with project context, categories, and tags into CEMS long-term memory
Store learnings, decisions, patterns, or preferences into CEMS memory with project context
| name | cems-foundation |
| description | View foundation guidelines (rules, principles, constraints) stored in CEMS memory |
Search CEMS memory for foundation guidelines — stable rules and principles that apply across all sessions.
CEMS MCP server must be configured. See github.com/Chocksy/cems for setup.
When this skill is invoked, or the user asks about project rules/guidelines:
Detect the current project from the working directory:
git remote get-url origin to extract org/repo formatgit@github.com:org/repo.git → org/repohttps://github.com/org/repo.git → org/repoSearch for foundation guidelines via MCP:
{
"tool": "memory_search",
"arguments": {
"query": "foundation guidelines rules principles constitution",
"max_results": 20,
"scope": "both",
"project": "org/repo"
}
}
Filter results to only include memories that:
Present results clearly:
## Foundation Guidelines
Found N foundation guidelines:
1. <guideline content>
2. <guideline content>
...
These are your foundational principles. They apply to all sessions.
Foundation guidelines are stable rules that apply across all sessions. They are typically:
They differ from regular memories in that they are meant to be always-on constraints, not just recalled information.