Token导航 LogoToken导航TokenDH.com
前端设计只读github未标认证来源可访问clear审计通过

gps-method全球定位系统方法

Agent Skill

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

总安装

490

周安装

20

GitHub Stars

17

下载量

158
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:gps-method(全球定位系统方法)
来源仓库:https://github.com/mintuz/claude-plugins
仓库路径:skills/gps-method
安装命令:
npx skills add https://github.com/mintuz/claude-plugins --skill gps-method
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/mintuz/claude-plugins --skill gps-method

简介

gps-method 用于辅助前端页面、组件、样式和交互逻辑的开发与维护。

  • 适合生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码。
  • 使用时需要结合项目现有设计系统、路由和构建方式,避免生成孤立片段。
  • 涉及页面改动时应配合本地预览和构建检查确认视觉效果。
  • gps-method 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

GPS Method - Goal Achievement Framework

An evidence-based framework for achieving any goal through systematic breakdown and execution. GPS stands for Goal, Plan, and System.

How This Works

The GPS method serves two purposes:

  1. Goal Creation: Guide users through defining clear goals and building actionable systems to achieve them
  2. Progress Diagnosis: When users struggle, identify exactly where the breakdown is occurring

Workflow Overview

Guide users through this sequence:

Mode 1: Creating a New Goal

  1. Define the Goal - Establish destination with specificity, motivation, and constraints
  2. Build the Plan - Identify major moves, assess feasibility, and forecast obstacles
  3. Design the System - Set up tracking, reminders, and accountability mechanisms
  4. Document Everything - Create a structured goal document for reference

Mode 2: Diagnosing Existing Goals

When a user is struggling with progress:

  1. Identify which component is broken (Goal, Plan, or System)
  2. Ask diagnostic questions specific to that component
  3. Recommend targeted fixes based on the diagnosis

Creating a New Goal

Step 1: Define the Goal (The Destination)

Guide the user through three factors:

Specificity and Concreteness

  • Avoid vague goals like "start a business" or "get fit"
  • Ask: "Can you make this more specific and measurable?"
  • Push for quantifiable outcomes: "reduce visceral fat by 50%" or "build a business making $100k/year"

Emotional Compulsion (The Why)

  • Explore intrinsic motivations
  • Ask: "Why does this matter to you personally?"
  • Watch for "should" goals driven by external pressure (fame, status, obligation)
  • Help distinguish between genuine desire and external expectations

Anti-Goals (Constraints)

  • Identify what they want to avoid while pursuing the goal
  • Ask: "What would you NOT be willing to sacrifice for this?"
  • Examples: "not working weekends", "not sacrificing family time", "not going into debt"

Step 2: Build the Plan (The Roadmap)

Guide the user through three components:

Major Moves (3-5 Primary Actions)

  • Ask: "What are the 3-5 main things you need to do to achieve this?"
  • Push for concrete, actionable steps
  • Example for weight loss: specific calorie targets, protein intake, number of weekly workouts
  • Example for business: revenue target, customer acquisition strategy, product timeline

Realistic Assessment

  • Test if the plan works in theory: "Will these actions actually produce the result?"
  • Test if the plan works in practice: "Are you actually likely to follow through?"
  • Use 80% confidence threshold: if below 80% on either, rethink the plan
  • Ask directly: "On a scale of 0-100%, how confident are you this will work?"

Crystal Ball Method (Mental Forecasting)

  • Have them imagine they failed in 6 months
  • Ask: "What are the top 3 reasons this didn't work out?"
  • For each failure reason, create a preemptive strategy
  • This builds in resilience before obstacles arise

Step 3: Design the System (The Execution)

Guide the user through three mechanisms:

Tracking

  • Ask: "How will you monitor progress?"
  • Suggest specific tools: Google Sheet, app, scale, journal
  • Explain: awareness of numbers nudges better micro-decisions
  • Make it as frictionless as possible

Reminders

  • Ask: "How will you remember to work on this daily?"
  • Suggest options:

- Write goals down each morning - Vision board in visible location - Calendar blocks for major moves - Phone reminders at key times

  • The brain forgets resolutions without cues

Accountability

  • Ask: "Who can help hold you accountable?"
  • Options: accountability buddy, squad, mentor, coach, public commitment
  • Most people struggle with self-accountability alone
  • External pressure and support are critical when motivation wanes

Documenting the Goal

Create a structured document using this template (see references/goal-template.md for full version):

# [Goal Name]

## Goal (The Destination)

**Specific Target**: [Quantifiable outcome]
**Why This Matters**: [Intrinsic motivation]
**Anti-Goals**: [What you won't sacrifice]

## Plan (The Roadmap)

**Major Moves**:

1. [Action 1]
2. [Action 2]
3. [Action 3]

**Confidence Assessment**:

- Theory (will it work?): [X]%
- Practice (will I do it?): [X]%

**Failure Forecast**:

- Potential obstacle 1 → Mitigation strategy
- Potential obstacle 2 → Mitigation strategy
- Potential obstacle 3 → Mitigation strategy

## System (The Execution)

**Tracking**: [How you'll measure]
**Reminders**: [How you'll remember]
**Accountability**: [Who will help]

Diagnosing Existing Goals

When a user is struggling, run through this diagnostic:

Question 1: Is the Goal clear?

  • Can they articulate it in one specific sentence?
  • If not → Work on Goal definition first

Question 2: Do they believe the Plan will work?

  • Are they confident in the major moves (theory)?
  • Are they confident they'll actually do them (practice)?
  • If not → Revise the Plan

Question 3: Are they executing the System?

  • Are they tracking?
  • Are they using reminders?
  • Do they have accountability?
  • If not → Strengthen the System

See references/diagnostic-guide.md for detailed troubleshooting questions.

The GPS Analogy

Help users understand through the literal GPS metaphor:

  • Goal = Destination you type into the GPS
  • Plan = Specific route chosen (highways vs. side streets)
  • System = Dashboard and steering wheel that keep you on the road and monitor fuel

Without all three, you can't reliably reach your destination.

Examples

For inspiration and quality standards, see references/example-goals.md for complete GPS breakdowns across different domains:

  • Fitness goals
  • Business goals
  • Learning goals
  • Relationship goals
  • Creative projects

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

24.9%
按下载量换算39

Antigravity

23.77%
按下载量换算38

Codex

16.62%
按下载量换算26

OpenCode

12.93%
按下载量换算20

Gemini CLI

7.69%
按下载量换算12

windsurf

2.95%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills