fix: Update README with current project names and links#58
fix: Update README with current project names and links#58LucasSantana-Dev merged 1 commit intomainfrom
Conversation
- Remove hardcoded version 1.2.0 (use badges instead) - Fix project names: forge-space-ui → siza, forge-space-mcp → siza-mcp - Fix broken relative links to use GitHub URLs - Fix npm package name: @uiforge/forge-patterns → @forgespace/core - Fix directory name in structure: uiforge-patterns → forge-patterns - Add siza-gen and branding-mcp to projects list
📝 WalkthroughWalkthroughThis PR updates the README.md file with project rebranding and reorganization, including renaming projects (uiforge-patterns to Forge Space/Siza components), updating installation commands, adjusting project listings, and refreshing documentation references. No code or API changes are introduced. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
186-189:⚠️ Potential issue | 🟡 MinorUpdate feature toggle examples to use new project names.
Lines 187-189 still reference the old project names
forge-space-uiandforge-space-mcp. These should be updated tosizaandsiza-mcprespectively to align with the current project rebranding used elsewhere in the README.Proposed fix
forge-features enable mcp-gateway.rate-limiting -forge-features enable forge-space-ui.rate-limiting -forge-features enable forge-space-mcp.ai-chat -forge-features enable forge-space-ui.dark-mode +forge-features enable siza.rate-limiting +forge-features enable siza-mcp.ai-chat +forge-features enable siza.dark-mode🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 186 - 189, Update the feature toggle examples by replacing the old project names in the CLI lines: change "forge-space-ui" to "siza" and "forge-space-mcp" to "siza-mcp" in the existing "forge-features enable" commands so the examples read "forge-features enable siza.rate-limiting" and "forge-features enable siza-mcp.ai-chat" (and similarly for the dark-mode toggle).
🧹 Nitpick comments (1)
README.md (1)
49-50: Consider using absolute GitHub URLs for consistency.The PR objectives mention replacing broken relative links with absolute GitHub URLs. While these relative links should work correctly (they point to files within the same repository), using absolute URLs would be more consistent with the stated approach and would make the links work in any context (e.g., when the README is viewed outside GitHub).
🔗 Proposed change to use absolute URLs
-- [**Documentation Hub**](docs/README.md) - Complete documentation -- [**Project Context**](docs/project/PROJECT_CONTEXT.MD) - Project guide and context +- [**Documentation Hub**](https://github.com/Forge-Space/core/blob/main/docs/README.md) - Complete documentation +- [**Project Context**](https://github.com/Forge-Space/core/blob/main/docs/project/PROJECT_CONTEXT.MD) - Project guide and context🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 49 - 50, Replace the two relative links in README.md (the link texts "Documentation Hub" and "Project Context") with absolute GitHub URLs pointing to the corresponding files in this repository (e.g., https://github.com/<owner>/<repo>/blob/main/docs/README.md and https://github.com/<owner>/<repo>/blob/main/docs/project/PROJECT_CONTEXT.MD), updating the markdown so the links work consistently outside the repo and follow the PR's objective of using absolute URLs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 46: The "Siza MCP" README link text ([**Siza MCP**]) currently points to
the wrong repository (ui-mcp); update the markdown link target to the correct
repo name (siza-mcp) so the link becomes the siza-mcp URL, mirroring the fix
applied at the earlier occurrence; locate the "[**Siza MCP**]" entry and replace
its href to use "siza-mcp" instead of "ui-mcp".
---
Outside diff comments:
In `@README.md`:
- Around line 186-189: Update the feature toggle examples by replacing the old
project names in the CLI lines: change "forge-space-ui" to "siza" and
"forge-space-mcp" to "siza-mcp" in the existing "forge-features enable" commands
so the examples read "forge-features enable siza.rate-limiting" and
"forge-features enable siza-mcp.ai-chat" (and similarly for the dark-mode
toggle).
---
Nitpick comments:
In `@README.md`:
- Around line 49-50: Replace the two relative links in README.md (the link texts
"Documentation Hub" and "Project Context") with absolute GitHub URLs pointing to
the corresponding files in this repository (e.g.,
https://github.com/<owner>/<repo>/blob/main/docs/README.md and
https://github.com/<owner>/<repo>/blob/main/docs/project/PROJECT_CONTEXT.MD),
updating the markdown so the links work consistently outside the repo and follow
the PR's objective of using absolute URLs.
| - [**Forge Space - UI MCP**](../uiforge-mcp/) - Specialized UI development tools | ||
| - [**Siza**](https://github.com/Forge-Space/siza) - AI-powered full-stack workspace | ||
| - [**MCP Gateway**](https://github.com/Forge-Space/mcp-gateway) - Central tool aggregation and routing | ||
| - [**Siza MCP**](https://github.com/Forge-Space/ui-mcp) - MCP server for UI generation |
There was a problem hiding this comment.
Critical: Same URL mismatch for Siza MCP.
The same issue as Line 29 - "Siza MCP" links to ui-mcp instead of siza-mcp.
🔗 Proposed fix for the URL
-- [**Siza MCP**](https://github.com/Forge-Space/ui-mcp) - MCP server for UI generation
+- [**Siza MCP**](https://github.com/Forge-Space/siza-mcp) - MCP server for UI generation📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - [**Siza MCP**](https://github.com/Forge-Space/ui-mcp) - MCP server for UI generation | |
| - [**Siza MCP**](https://github.com/Forge-Space/siza-mcp) - MCP server for UI generation |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` at line 46, The "Siza MCP" README link text ([**Siza MCP**])
currently points to the wrong repository (ui-mcp); update the markdown link
target to the correct repo name (siza-mcp) so the link becomes the siza-mcp URL,
mirroring the fix applied at the earlier occurrence; locate the "[**Siza MCP**]"
entry and replace its href to use "siza-mcp" instead of "ui-mcp".
Summary
forge-space-ui,forge-space-mcp) to current (siza,siza-mcp)../uiforge-webapp/,../../ECOSYSTEM_OVERVIEW.md) to GitHub URLs@uiforge/forge-patternsto@forgespace/coreuiforge-patterns/toforge-patterns/Test plan
uiforge-*naming🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation