Writing Skills
writing-skills
效率与协作技能,来自 obra/superpowers,查看原文获取完整用途和操作说明。
paddlevit【部署与运维】Guide PaddleViT computer-vision workflows for transformer and MLP image classification, object detection, semantic segmentation, DINO self-supervision, GANs, configuration, distributed/AMP execution, and Paddle deployment with explicit data, backend, and checkpoint boundaries.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this skill when a task names PaddleViT/PPViT, its standalone model
folders, PaddlePaddle vision transformers, or a workflow that matches one of
its classification, detection, segmentation, self-supervised, GAN, or export
surfaces. PaddleViT is a collection of source-rooted projects, not one
installable Python package: each model folder commonly has its own config.py,
model module, dataset code, and entry script.
Before writing a command, record:
BASE files, data root/split, checkpoint prefix, and
output directory;cpu, one CUDA device, or distributed CUDA), budget, and
whether downloads or long training are permitted;Run the read-only environment probe before attributing failures to a model:
python scripts/check_paddlevit_environment.py --help
python scripts/check_paddlevit_environment.py --json
Install PaddlePaddle using the official wheel that matches the host and CUDA
runtime. The repository documents PaddlePaddle 2.1-era APIs; current releases
may need a per-model smoke or a small compatibility patch. Add yacs and
pyyaml for the shared configuration pattern. Segmentation additionally uses
OpenCV, SciPy, and cityscapesScripts; COCO detection uses pycocotools; GAN
LSUN workflows use lmdb. Do not install every optional dependency or download
weights/data merely to inspect a config.
Read model-catalog.md when a request does not name a model family. Read configuration.md when YAML, CLI overrides, source-root imports, or checkpoint paths are involved. Read troubleshooting.md before retrying an import, backend, data, export, or checkpoint failure.
Run one family in one fresh process. Put only the selected model directory (and
its documented sibling utilities) on PYTHONPATH; many folders contain bare
modules named config, datasets, utils, or models. Never combine several
model directories in one interpreter and assume imports are unambiguous.
Generated helper scripts are source-independent and must not be used as proof
that a source model's current API is compatible.
A config parse, dependency import, or tiny CPU forward does not prove CUDA, AMP, distributed, dataset, checkpoint, or benchmark behavior. For GPU claims, run a tiny operation on the requested CUDA device. For a real metric, require a real compatible split and checkpoint. Treat training, multi-scale/slide segmentation, COCO evaluation, DINO ImageNet pretraining, GAN FID, multi-GPU launch, export, quantization, and cross-framework porting as explicit operations with an approved output path and stop condition.
Do not overwrite checkpoints, delete demo output trees, mutate a dataset, or fetch external weights/data without explicit authorization. Prefer a new output prefix and read-only preflight. Record the source commit and effective config in any downstream experiment handoff; consult repo-provenance.md before deciding whether a checkout is stale.