Skip to main content

fgeo

Languages: English | 简体中文

fgeo is not just a software system.

It is a learning methodology, packaged as an out-of-the-box agent skill, that helps you turn real work into growth.

fgeo is built around one formula:

User Growth = Action x Feedback x Adaptation

You grow when you do something real, receive meaningful feedback, and change the next attempt.

What fgeo Is

fgeo is a local-first growth companion for AI-assisted work.

It helps an agent understand your goal, route the work to the right skill, and keep the learning loop alive:

Action -> Feedback -> Adaptation

The CLI provides the local state boundary. The agent skills provide the methodology and workflow guidance.

Together, they help you:

  • understand your current level and what is worth improving next,
  • practice through small real attempts,
  • turn learning into reusable records, cases, and content,
  • publish content and route real-world signals back into learning,
  • avoid starting from zero every time you open a new agent session.

Why the Formula Matters

The formula uses multiplication because any missing part breaks the loop:

  • Action without Feedback becomes blind repetition.
  • Feedback without Action becomes analysis without experience.
  • Action plus Feedback without Adaptation becomes awareness without growth.

Time and memory are not the formula itself. Time only matters when useful loops repeat. Memory helps fgeo preserve prior signals, reuse context, and time the next loop so each session does not start from zero.

fgeo Agent Skills

fgeo routes user intent into one primary workflow at a time:

need clarity / current level / review / feedback meaning -> fgeo-digest
need practice / improvement / mastery / next attempt     -> fgeo-growth
need expression / draft / story / case / article         -> fgeo-content
need publish / external signal / metrics / reply         -> fgeo-publish
need identity / audience / preference / boundary         -> fgeo-profile

Each skill supports a different part of the learning loop:

Skill Role
fgeo-digest Interprets what happened, what is clear, what is shaky, and what feedback means.
fgeo-growth Turns goals or gaps into small practice, review, and the next better attempt.
fgeo-content Turns learning, evidence, cases, and methods into platform-native expression.
fgeo-publish Publishes tracked content and routes real-world signals back into learning.
fgeo-profile Preserves identity, preferences, audience, boundaries, and long-term context.

Why This Matters

Most AI tools help with a single task:

summarize this
write this
publish this
fix this

fgeo tries to help with continuous growth:

What did I do?
What feedback appeared?
What did I not notice?
What should I absorb?
What should change next time?

The feedback loop is not a closing CTA. It is the core learning mechanism. fgeo should help the user notice signals they missed, absorb those signals, and turn them into the next action.

CLI Quick Start

Install and initialize fgeo:

pip install fgeo

fgeo init
fgeo enable codex

Create a project and publishing workflow:

fgeo project create fcontext --desc "AI context manager"
fgeo goal add fcontext "Help developers understand fcontext"
fgeo platform add fcontext devto --directions "tutorial,architecture" --pace "2/month"
fgeo plan create fcontext cold-start --strategy "Developer community launch"
fgeo plan assign fcontext cold-start devto --direction tutorial --target 3

Register content:

fgeo content register docs/first-post.md \
  --project fcontext \
  --platform devto \
  --plan cold-start \
  --direction tutorial \
  --type article \
  --status draft

Check status:

fgeo status fcontext

What the CLI Manages

The CLI keeps stable local state for the agent skills:

Profile -> Digest -> Growth -> Content -> Publish -> Feedback

It can track projects, goals, plans, platforms, content assets, publish tasks, learning records, evidence, gaps, baselines, and feedback signals.

The important point is not the database. The important point is that the agent does not lose the learning loop between sessions.

Supported Agent Integrations

fgeo enable <agent> writes fgeo instructions into each agent's native location and also enables fcontext for the same workspace.

Supported agents:

copilot, claude, cursor, trae, qwen, kiro, opencode,
openclaw, zed, pi, antigravity, codex

Metadata

Release files for fgeo 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fgeo 1.0.0
File Size Uploaded
fgeo-1.0.0.tar.gz 185.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for fgeo 1.0.0
File Interpreter ABI Platform
fgeo-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 325.5 kB

Release files / fgeo-1.0.0.tar.gz

Download URL fgeo-1.0.0.tar.gz
Size 185.0 kB
Tags Source
SHA-256 checksum
How to use checksums
1ecc04935ba94a3c848f2179c4a7e2ba7c2b34896a225869213afecc85ebfcfd
BLAKE2b-256 checksum
How to use checksums
fe88c39fe78588792a66352e1924f7f64b5f3e7e7d6d27774b0abb871b3103ce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.

Transparency log

Release files / fgeo-1.0.0-py3-none-any.whl

Download URL fgeo-1.0.0-py3-none-any.whl
Size 140.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8e60bd2eab16a0a8ef98141fac034dca8fb55a3ca5fbd74a306ef0a591799e3e
BLAKE2b-256 checksum
How to use checksums
74b468ca1deb3432a0328160bbd244c992d2dea53f4229f8a4b9de2238b5e823
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page