Token导航 LogoToken导航

Agent Skill · 开发规范

reactlynx-best-practices(Reactlynx 最佳实践)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

reactlynx-best-practices 是开发规范类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为可写文件;许可证信息还不明确,第三方扫描有未通过项,按安装量在开发规范类的 1,265 个 Skill 里排第 545。

总安装 1,004周安装 41GitHub Stars 21下载 325核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:reactlynx-best-practices(Reactlynx 最佳实践)
来源仓库:https://github.com/lynx-community/skills
仓库路径:skills/reactlynx-best-practices
安装命令:
npx skills add https://github.com/lynx-community/skills --skill reactlynx-best-practices
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/lynx-community/skills --skill reactlynx-best-practices

这个 Skill 是做什么的

开发规范类 Skill 用来统一代码风格、目录结构和评审口径,产出多为检查清单或改写建议。

用于辅助 ReactLynx 开发规范的制定与执行,适合在 Codex、Claude、Cursor、Gemini CLI 中快速检查代码风格与架构合理性。支持提供组件拆分建议、状态管理规范和安全编码准则,提升项目质量。

通过 npx skills add 命令从指定仓库安装,需确认本地环境是否支持 GitHub 技能加载。使用前建议核对项目路由、构建配置及测试框架版本,避免只生成孤立片段。涉及页面改动时,应配合本地预览和构建检查,确认视觉效果与交互行为一致。

来源仓库内路径:skills/reactlynx-best-practices

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/lynx-community/skills --skill reactlynx-best-p…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要可写文件,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

reactlynx-best-practices 怎么安装?

在终端执行 npx skills add https://github.com/lynx-community/skills --skill reactlynx-best-practices。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

reactlynx-best-practices 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

reactlynx-best-practices 需要什么权限?

权限级别是可写文件。该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

reactlynx-best-practices 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

reactlynx-best-practices 用的人多吗?

公开数据是累计安装 1,004 次,近一周安装 41 次,下载 325 次,GitHub 21 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

reactlynx-best-practices 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发规范类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发规范类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
vercel-react-best-practices

Vercel React 最佳实践 · Codex、Claude

8,490,72025,918操作浏览器MIT通过
web-design-guidelines

网页设计指南 · Codex、Claude

6,686,01625,885需要联网MIT有提醒
remotion-best-practices

Remotion 最佳实践 · Codex、Claude

6,505,6323,027操作浏览器MIT有提醒
supabase-postgres-best-practices

Supabase Postgres 最佳实践 · Codex、Claude

3,175,5232,030需要联网MIT通过
next-best-practices

Next.js 最佳实践 · Codex、Claude

1,848,240841操作浏览器MIT通过
reactlynx-best-practices

Reactlynx 最佳实践 · 本页

1,00421可写文件未明确未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

ReactLynx Best Practices

ReactLynx best practices covering dual-thread architecture and React patterns. Provides rules reference for writing, static analysis for reviewing, and auto-fix for refactoring.

When to Apply

This skill should be used when:

  • Writing new ReactLynx components or application → Reference rules as guidelines
  • Reviewing existing ReactLynx code → Use scanner to detect issues
  • Refactoring ReactLynx code → Use auto-fix with user approval

Input

This skill accepts the following inputs:

InputRequiredDescription
sourceCodeNoThe ReactLynx source code to analyze (string or file path)
modeNoWorkflow mode: writing, review, or refactor. Auto-detected if not specified

Mode Auto-Detection

When mode is not explicitly provided, the skill will determine the appropriate mode based on context:

ContextAuto-Selected Mode
User is asking for best practices or guidelineswriting
User wants to check/analyze existing code for issuesreview
User wants to fix/refactor code with auto-fixesrefactor

Workflow Modes

📝 Writing Mode

When writing new ReactLynx code, reference the rules in rules/*.md as best practice guidelines. See also the Rules section below for a summary of all available rules.

Use this mode when:

  • User is creating new ReactLynx components or application
  • User asks "how should I write..." or "what's the best practice for..."
  • No existing code to analyze

🔍 Review Mode

When reviewing code, do both:

  1. Use the scanner (scripts/index.mjs) to analyze source code for issues
  2. Combine findings with rules/*.md explanations to generate a rule-aware report

Use this mode when:

  • User provides code and asks to "check", "review", or "analyze" it
  • User wants to know if their code has any issues
  • User asks "is this code correct?" or "any problems with this?"

Report requirements (must include):

  • Scan summary from workflow.reviewCode(sourceCode)
  • Rule interpretation for each hit ruleId from rules/<ruleId>.md
  • Severity/impact context from rule metadata (impact, impactDescription)
  • Actionable suggestions based on rule guidance (not only raw diagnostics)
node -e "
import fs from 'fs';
import { ReactLynxWorkflow, formatScanReport } from '<path_to_skill>/scripts/index.mjs';

// <sourceCode>: string (source code) or file path
const input = '<sourceCode>';
const sourceCode = fs.existsSync(input) ? fs.readFileSync(input, 'utf-8') : input;

const workflow = new ReactLynxWorkflow('review');
const summary = workflow.reviewCode(sourceCode);
console.log(formatScanReport(summary));
"

🔧 Refactor Mode

When refactoring, generate a fix plan and ask the user before applying. In this mode, output must include both script results and a rules-aware report.

Use this mode when:

  • User explicitly asks to "fix", "refactor", or "auto-fix" code
  • User wants to apply suggested fixes from a previous review
  • User says "please fix these issues" or "apply the fixes"

Report requirements (must include):

  • Pre-fix scan summary and rule-aware interpretation
  • Fix plan summary (fixableIssues, manualIssues, per-file changes)
  • Post-fix outcome (appliedFixes) and remaining manual issues
TOOL CALL: AskUserQuestion(
  question: "🔧 Found {fixableIssues} auto-fixable issues. Would you like me to apply these fixes?",
  options: ["Yes, apply fixes", "No, show me the issues first", "Skip auto-fix"]
)
node -e "
import fs from 'fs';
import { ReactLynxWorkflow, formatFixPlan } from '<path_to_skill>/scripts/index.mjs';

// <sourceCode>: string (source code) or file path
const input = '<sourceCode>';
const sourceCode = fs.existsSync(input) ? fs.readFileSync(input, 'utf-8') : input;

const workflow = new ReactLynxWorkflow('refactor');
workflow.reviewCode(sourceCode);
const plan = workflow.generateFixPlan();

if (plan && plan.fixableIssues > 0) {
  console.log(formatFixPlan(plan));
  // ASK USER: 'Would you like me to apply these auto-fixes?'
  // If yes:
  const { fixed, appliedFixes } = workflow.applyAutoFixes(sourceCode);
  console.log('Fixed code:', fixed);
}
"

Rules

All rules are documented in the rules/ directory as Markdown files:

RuleImpactDescription
detect-background-onlyCRITICALNative APIs in background contexts, use 'background only' directive
proper-event-handlersMEDIUMCorrect event handler usage
main-thread-scripts-guideMEDIUMMain thread scripts guide
hoist-static-jsxLOWPerformance optimization

API Reference

For complete type definitions:

TOOL CALL: Read(<path_to_skill>/scripts/index.d.ts)

Exported Functions

function runSkill(source: string): Diagnostic[];
function runSkillWithFixes(source: string): DiagnosticWithFix[];
function analyzeBackgroundOnlyUsage(source: string): Diagnostic[];
function generateFixes(source: string, diagnostic: Diagnostic): Fix[];
function applyFix(source: string, fix: Fix): string;
function applyFixes(source: string, fixes: Fix[]): string;
function formatScanReport(summary: ScanSummary): string;
function formatFixPlan(plan: FixPlan): string;

Workflow Class

class ReactLynxWorkflow {
  constructor(mode: WorkflowMode);
  reviewCode(source: string): ScanSummary;
  generateFixPlan(): FixPlan | null;
  applyAutoFixes(source: string): { fixed: string; appliedFixes: Fix[] };
}

Key Types

type WorkflowMode = 'writing' | 'review' | 'refactor';

interface Diagnostic {
  ruleId: string;
  message: string;
  severity: 'error' | 'warning' | 'info';
  location: { start: { line: number; column: number }; end: { line: number; column: number } };
}

interface DiagnosticWithFix extends Diagnostic {
  fixes?: Fix[];
}

interface Fix {
  type: 'wrap-in-useEffect' | 'add-directive' | 'add-import' | 'move-to-event-handler';
  description: string;
  oldCode: string;
  newCode: string;
  location: { start: { line: number; column: number }; end: { line: number; column: number } };
}

interface ScanSummary {
  totalFiles: number;
  filesWithIssues: number;
  totalIssues: number;
  errorCount: number;
  warningCount: number;
  infoCount: number;
  results: ScanResult[];
}

interface FixPlan {
  totalIssues: number;
  fixableIssues: number;
  manualIssues: number;
  files: FilePlan[];
}

平台分布

Codex

33.84%
按下载量换算110

Claude

31.1%
按下载量换算101

Cursor

18.2%
按下载量换算59

Gemini CLI

8.66%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

可写文件

该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills