Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

nexus-project-rules

Estrelas6

Forks0

Atualizado1 de março de 2026 às 21:18

Core architectural rules, tech stack, and privacy constraints for Project Nexus. Use this skill whenever starting a new task, making architectural decisions, generating project structures, or reviewing code.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

MAX-786

MAX-786/project-nexus

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	nexus-project-rules
description	Core architectural rules, tech stack, and privacy constraints for Project Nexus. Use this skill whenever starting a new task, making architectural decisions, generating project structures, or reviewing code.

Project Nexus: Core Architecture & Rules

Tech Stack

Web App: Next.js (App Router), React 18+, TypeScript.
UI: TailwindCSS, Shadcn UI, Lucide Icons.
Extension: Plasmo framework (React, TypeScript).
Database: Supabase (PostgreSQL), pgvector.
Visualization: React Flow.

Privacy & BYOK (Bring Your Own Key) Strict Rules

Project Nexus is an open-source, privacy-first tool.

Never route user LLM API keys through our backend/Next.js server for Free Tier users.
API calls to OpenAI/Anthropic/Gemini MUST happen directly from the client (Browser Extension or Browser DOM) using the Vercel AI SDK.
API keys must be stored strictly in the browser's local storage or Plasmo's Secure Storage API.

File Structure Conventions

apps/web/ - The Next.js web application.
apps/extension/ - The Plasmo browser extension.
packages/shared/ - Shared TypeScript types matching the Supabase schema.

Coding Standards

Use strict TypeScript. No any types.
Fail gracefully. If an API call fails or a webpage DOM cannot be scraped, return a user-friendly error toast, do not crash the application.

Mais deste repositório

mesmo repositório

nexus-docs-manager

MAX-786/project-nexus

Rules for creating, updating, and managing project documentation. Use this skill when analyzing Git commits, updating the README, writing API specs, or acting as the Technical Writer for Project Nexus.

2026-03-096

nexus-github-cli

MAX-786/project-nexus

Act as an autonomous project manager and lead developer. Use the GitHub CLI (`gh`) to orchestrate the entire development lifecycle: tracking tasks on Project Boards, organizing Sprints via Milestones, documenting progress via Issue Comments, and executing code changes via Pull Requests.

2026-03-046

nexus-code-quality

MAX-786/project-nexus

Rules for ESLint, Prettier, and TypeScript strictness. Use this skill when writing new files, refactoring code, or debugging build failures caused by type errors.

2026-03-046

nexus-deployments

MAX-786/project-nexus

Deployment protocols for Vercel (Next.js Web App), Chrome Web Store packaging (Plasmo Extension), and Supabase production migrations. Use this when setting up CI/CD, preparing a release, or configuring deployment environment variables.

2026-03-046

nexus-git-workflow

MAX-786/project-nexus

Guidelines for Git branching, commit messages (Conventional Commits), and Pull Request structures. Use this skill when asked to commit code, create a branch, or write a PR description.

2026-03-046

nexus-marketing-growth

MAX-786/project-nexus

Guidelines for generating marketing copy, Reddit posts, Hacker News launches, and growth strategies for Project Nexus. Use this skill when asked to write public-facing content, launch announcements, or analyze product-market fit.

2026-03-026

name	nexus-project-rules
description	Core architectural rules, tech stack, and privacy constraints for Project Nexus. Use this skill whenever starting a new task, making architectural decisions, generating project structures, or reviewing code.

Project Nexus: Core Architecture & Rules

Tech Stack

Web App: Next.js (App Router), React 18+, TypeScript.
UI: TailwindCSS, Shadcn UI, Lucide Icons.
Extension: Plasmo framework (React, TypeScript).
Database: Supabase (PostgreSQL), pgvector.
Visualization: React Flow.

Privacy & BYOK (Bring Your Own Key) Strict Rules

Project Nexus is an open-source, privacy-first tool.

Never route user LLM API keys through our backend/Next.js server for Free Tier users.
API calls to OpenAI/Anthropic/Gemini MUST happen directly from the client (Browser Extension or Browser DOM) using the Vercel AI SDK.
API keys must be stored strictly in the browser's local storage or Plasmo's Secure Storage API.

File Structure Conventions

apps/web/ - The Next.js web application.
apps/extension/ - The Plasmo browser extension.
packages/shared/ - Shared TypeScript types matching the Supabase schema.

Coding Standards

Use strict TypeScript. No any types.
Fail gracefully. If an API call fails or a webpage DOM cannot be scraped, return a user-friendly error toast, do not crash the application.