Skip to content

Conversation

@aRustyDev
Copy link
Owner

Summary

  • Removes legacy/ (2,067 files), .todo/ (792 files), components/ (721 files), and unused scaffold dirs — content previously migrated or no longer needed
  • Adds context/ as the canonical home for skills, agents, commands, hooks, rules, and plugins
  • Adds context/.context/ for research/reference material (claude-cookbooks, context-engineering-intro, etc.)
  • Adds assets/ (sounds, mustache templates), build/ (output targets), settings/ (editor configs), .beads/ (interaction tracking)
  • Adds .gitattributes and AGENTS.md

Test plan

  • Verify context/skills/ contains all expected skills
  • Verify legacy/, .todo/, components/, .templates/, tools/, mcp/ are fully removed
  • Verify build/, settings/, assets/ scaffolding is present
  • Spot-check that no content was lost (skills in context/skills/ match former components/skills/)

🤖 Generated with Claude Code

aRustyDev and others added 12 commits January 31, 2026 01:16
Content previously reorganized into context/, build/, and settings/.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Third-party repos and reference material previously staged for
evaluation (claude-cookbooks, context-engineering-intro,
claude-code-spec-workflow, super-claude-framework, etc.).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Skills, commands, rules, hooks, and settings relocated to the
context/ directory structure.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Remove .templates/, .ctx/sitemap.xml, tools/, mcp/, schemas/,
profiles/ placeholders, and top-level main.py.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Includes category definitions, research repos (claude-code-dev-kit,
claude-cookbooks, context-engineering-intro, super-claude-framework),
and context sitemap.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Skills migrated from components/skills/ with updated directory
structure. Includes all language, CI/CD, meta, method, and
domain-specific skills.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Migrated from components/ and legacy/ directories.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Config, metadata, and interaction logs for session tracking.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sound files for notifications and mustache templates relocated
from .templates/.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Build target directories for claude, claude-code, cortex, gemini,
vscode, and zed.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Editor and tool settings (claude, cursor, vscode, windsurf, zed)
and build configuration TODO.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm ioredis is 96.0% likely obfuscated

Confidence: 0.96

Location: Package overview

From: ?npm/probot@13.4.7npm/ioredis@5.9.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ioredis@5.9.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm markdown-it is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: context/.context/context-engineering-intro/use-cases/mcp-server/package-lock.jsonnpm/workers-mcp@0.0.13npm/markdown-it@14.1.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm vite is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: context/.context/context-engineering-intro/use-cases/mcp-server/package-lock.jsonnpm/vitest@3.2.4npm/vite@7.0.4

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vite@7.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@aRustyDev aRustyDev merged commit 629f384 into main Jan 31, 2026
4 checks passed
@aRustyDev aRustyDev deleted the refactor/repo-reorganization branch January 31, 2026 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant