AGENT SKILL

app-development

Help users author and customize Flower Apps with ServerApp, ClientApp, Context, Message, records, and pyproject.toml wiring.

License 许可
Apache-2.0
最近更新
2026-09-03
Stars
★ 351
Forks
27

01 前言 Front Matter

name
app-development
license
Apache 2.0
metadata
{ "disco-role": "operating" }
description
Help users author and customize Flower Apps with ServerApp, ClientApp, Context, Message, records, and pyproject.toml wiring.
disable-model-invocation
true

02 资源文件 4

03 SKILL.md 正文

app-development

Use this sub-skill for Flower App authoring, inspection, and troubleshooting.

Covers

  • ServerApp, ClientApp, Context, Message, RecordDict, ArrayRecord, ConfigRecord, MetricRecord, and Array
  • pyproject.toml app metadata and tool.flwr.app.components
  • flwr new / flwr run app authoring loops
  • Context.run_config, Context.node_config, and Context.state
  • lifecycle hooks via lifespan()
  • legacy compatibility and deprecation notes for app wiring

Does not cover

  • strategy internals
  • dataset partitioning
  • deployment admin
  • repo-maintenance commands

Start here

  1. Read references/workflows.md.
  2. Check references/api-reference.md for exact signatures and routing rules.
  3. Use references/troubleshooting.md for signature, config, and record-type failures.
  4. Run scripts/check_flower_app.py for a safe pyproject/component validation and tiny runtime smoke.

Quick routing

  • Server orchestration and round entry point: ServerApp
  • Client message handlers: ClientApp
  • Runtime settings and node-local data: Context
  • App payloads: Message and RecordDict
  • Arrays, configs, and metrics: ArrayRecord, ConfigRecord, MetricRecord

Practical rule of thumb

Keep app objects stateless. Put per-run memory in context.state, read run-specific values from context.run_config, and read node-specific values from context.node_config.

04 同仓库更多 Skills

VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-triton-opt

Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-solve

END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-skill

PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-pattern-fusion

Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-orchestrate

Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-feedback

Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).

★ 351