원클릭으로 Manus에서 모든 스킬 실행

lumina-frontend-ui

스타41

포크14

업데이트2026년 2월 28일 03:43

Build, refine, and debug the React/Vite frontend for Lumina. Use when editing files under client/src or client/package.json, changing chat UX, landing page content, auth flows, routing, theme behavior, markdown rendering, animations, responsive layout, or frontend API wiring.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

hoangsonww

hoangsonww/AI-RAG-Assistant-Chatbot

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Lumina Frontend UI

Overview

Use this skill for frontend tasks in client/. Keep changes aligned with Lumina's existing visual language: animated, polished, content-rich, and responsive rather than generic dashboard UI.

Load The Right Reference

Read references/component-map.md before editing when you need to locate the right page, component, or client-side service.
Read references/validation.md before finishing when frontend behavior, build health, or API coupling changed.

Work The Frontend Deliberately

Start from the user-facing entry point, then trace inward. For chat issues this usually means client/src/pages/Home.tsx plus client/src/components/ChatArea.tsx and client/src/services/api.ts.
Keep route-level changes consistent with client/src/App.tsx.
Prefer focused edits to the page or component that owns the behavior instead of broad global rewrites.
Treat client/src/pages/LandingPage.tsx as intentionally branded and heavily customized. Preserve its personality unless the task explicitly asks for a redesign.
Keep responsive behavior intact on mobile and desktop.
Keep markdown, math, and citation rendering working when changing chat output.

Coordinate With The Backend Carefully

If a frontend change depends on a new request shape, endpoint, or response contract, update the backend and openapi.yaml in the same task when feasible.
If the bug is really caused by retrieval, citations, or chat response composition, switch to lumina-rag-knowledge or lumina-backend-api instead of forcing a frontend-only patch.

Finish With Real Validation

Run npm run build in client/ after meaningful frontend changes.
Treat npm test in client/ as a placeholder, not as evidence of coverage.
Call out any unverified browser behavior if you could not run the app interactively.

이 저장소의 다른 Skills

같은 저장소

lumina-infra-deploy

hoangsonww/AI-RAG-Assistant-Chatbot

Work on Lumina deployment and infrastructure assets. Use when editing terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, ADVANCED_DEPLOYMENTS.md, agentic_ai/deployments/, or other files related to Docker, Terraform, AWS or Azure rollout behavior, environment wiring, and release automation.

2026-03-3141

lumina-agentic-mcp

hoangsonww/AI-RAG-Assistant-Chatbot

Work on the Python multi-agent pipeline and MCP client in agentic_ai. Use when editing files under agentic_ai/, changing agent orchestration, configuration loading, MCP client connectivity, async execution flow, pipeline startup commands, or cloud deployment wrappers for the Python service.

2026-03-1841

lumina-mcp-server

hoangsonww/AI-RAG-Assistant-Chatbot

Develop and maintain the standalone Lumina MCP server. Use when editing files under mcp_server/, adding or modifying tools, resources, prompts, middleware, configuration, or transport behavior for the Model Context Protocol server.

2026-03-1841

lumina-backend-api

hoangsonww/AI-RAG-Assistant-Chatbot

Implement and debug the Express and TypeScript backend for Lumina. Use when editing files under server/src or server/package.json, changing authentication, conversations, guest flows, chat routes, models, middleware, API contracts, or Gemini and Pinecone service wiring outside the dedicated knowledge-ingestion workflow.

2026-02-2841

lumina-rag-knowledge

hoangsonww/AI-RAG-Assistant-Chatbot

Manage Lumina's retrieval-augmented generation and knowledge ingestion workflow. Use when editing server/src/services/knowledgeBase.ts, server/src/services/pineconeClient.ts, server/src/scripts/knowledgeCli.ts, server/src/models/KnowledgeSource.ts, files under server/knowledge, manifest-based sync inputs, or debugging grounded answers, retrieval relevance, source lifecycle, and inline citations.

2026-02-2841

name	lumina-frontend-ui
description	Build, refine, and debug the React/Vite frontend for Lumina. Use when editing files under client/src or client/package.json, changing chat UX, landing page content, auth flows, routing, theme behavior, markdown rendering, animations, responsive layout, or frontend API wiring.

Lumina Frontend UI

Overview

Use this skill for frontend tasks in client/. Keep changes aligned with Lumina's existing visual language: animated, polished, content-rich, and responsive rather than generic dashboard UI.

Load The Right Reference

Read references/component-map.md before editing when you need to locate the right page, component, or client-side service.
Read references/validation.md before finishing when frontend behavior, build health, or API coupling changed.

Work The Frontend Deliberately

Start from the user-facing entry point, then trace inward. For chat issues this usually means client/src/pages/Home.tsx plus client/src/components/ChatArea.tsx and client/src/services/api.ts.
Keep route-level changes consistent with client/src/App.tsx.
Prefer focused edits to the page or component that owns the behavior instead of broad global rewrites.
Treat client/src/pages/LandingPage.tsx as intentionally branded and heavily customized. Preserve its personality unless the task explicitly asks for a redesign.
Keep responsive behavior intact on mobile and desktop.
Keep markdown, math, and citation rendering working when changing chat output.

Coordinate With The Backend Carefully

If a frontend change depends on a new request shape, endpoint, or response contract, update the backend and openapi.yaml in the same task when feasible.
If the bug is really caused by retrieval, citations, or chat response composition, switch to lumina-rag-knowledge or lumina-backend-api instead of forcing a frontend-only patch.

Finish With Real Validation

Run npm run build in client/ after meaningful frontend changes.
Treat npm test in client/ as a placeholder, not as evidence of coverage.
Call out any unverified browser behavior if you could not run the app interactively.