一键在 Manus 中运行任何 Skill

build-julia-interfaces

星标30

分支6

更新时间2026年7月9日 23:52

Build and repair Julia user interfaces: simple scripts and installable command-line apps, Comonicon-based command trees in compatible existing projects, styled terminal output and Term.jl live widgets, and custom Makie 0.24 plot recipes. Use for CLI entry points, options and subcommands, terminal reports or TUIs, package plotting extensions, and focused interface tests; use the workload skill instead for subprocess, pipeline, task, or thread mechanics.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Krastanov

Krastanov/JuliaLLMAgentSkills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Build Julia Interfaces

Start with the smallest interface that meets the user-facing contract. Keep domain logic in ordinary functions and make each interface a thin adapter.

Route the Task

Choose between a script, Base @main, experimental Pkg apps, and Comonicon: read references/cli.md.
Add styled terminal output, progress, or a Term live application: read references/term.md.
Extend Makie with a type conversion or full plot recipe: read references/makie-recipes.md.
Test argument handling, rendered output, live layouts, or recipes: read references/testing.md.

Open only the references required by the task.

Apply These Defaults

For one small command, use a plain Julia function plus Base @main on Julia 1.11+.
Use a Pkg app only on Julia 1.12+ when package installation is part of the requirement and the project accepts that Pkg app support is currently experimental.
Add a CLI framework only for meaningful parsing, help, completion, or subcommand needs. Keep Comonicon for compatible existing projects; do not make it the default.
Use plain text first, Term renderables second, and a Term live app only when keyboard interaction or continuously updated layout is required.
Use PrettyTables, via handle-julia-data, for ordinary tabular reports. Use Term.Tables.Table only inside a Term composition.
Target Makie 0.24's ComputeGraph for new reactive recipes. Do not copy pre-0.24 Observable mutation patterns into new code.
Test pure interface logic with explicit argument vectors and IOBuffers. Avoid elaborate mocks; add a small end-to-end smoke test only where the installed command contract matters.

For Cmd, environment, pipeline, process-I/O, deadlock, task, or thread details, use orchestrate-julia-workloads, especially its references/commands-and-processes.md file.

同仓库更多 Skills

同仓库

document-repository-v-model

Krastanov/JuliaLLMAgentSkills

Build, migrate, audit, review, update, and compact agent-facing repository documentation with nested AGENTS.md routers, selectively loaded Diátaxis-style .agents context, structured V-model specifications, and bidirectional verification traceability. Use when creating documentation for a new or existing repository, migrating a monolithic AGENTS.md, defining or auditing V-model traceability, interviewing developers to recover intended behavior, adding nested AGENTS.md files, organizing agent context, reviewing .agents consistency, or compacting stale and duplicated repository context.

2026-07-2430

develop-julia-packages

Krastanov/JuliaLLMAgentSkills

Develop and maintain Julia packages, including Project.toml and package layout changes, dependencies and compatibility, extensions, ParallelTestRunner-first tests, existing TestItemRunner suites, Documenter docs and doctests, JET/Aqua/coverage checks, Scratch runtime data, debugging, CI, and contribution workflows. Use for Julia package repositories and files such as Project.toml, Manifest.toml, src/*.jl, ext/*.jl, test/runtests.jl, docs/make.jl, and Julia GitHub Actions.

2026-07-0930

handle-julia-data

Krastanov/JuliaLLMAgentSkills

Build and repair focused Julia data workflows that consume Tables.jl sources, transform tabular data with DataFrames.jl, read or write delimited files with CSV.jl, handle TOML or YAML configuration, and render ordinary reports with PrettyTables.jl. Use for CSV/TSV ingestion, table transformations, configuration serialization, schema validation, and terminal/Markdown/HTML table output; do not use as a general statistics, database, plotting, or machine-learning guide.

2026-07-0930

optimize-julia-code

Krastanov/JuliaLLMAgentSkills

Measure and improve Julia runtime performance with BenchmarkTools, profiling and allocation tools, inference diagnosis, data-layout changes, and guarded low-level optimizations. Use when Julia code is slow, allocation-heavy, type-unstable, or needs a reproducible performance baseline or regression check.

2026-07-0930

orchestrate-julia-workloads

Krastanov/JuliaLLMAgentSkills

Coordinate Julia tasks, channels, threads, external numerical-library threads, and subprocesses with explicit lifetimes and failure propagation. Use when building producer-consumer workflows, parallelizing CPU work, fixing races or deadlocks, controlling oversubscription, or automating external commands from Julia.

2026-07-0930

name

build-julia-interfaces

description

Build Julia Interfaces

Start with the smallest interface that meets the user-facing contract. Keep domain logic in ordinary functions and make each interface a thin adapter.

Route the Task

Choose between a script, Base @main, experimental Pkg apps, and Comonicon: read references/cli.md.
Add styled terminal output, progress, or a Term live application: read references/term.md.
Extend Makie with a type conversion or full plot recipe: read references/makie-recipes.md.
Test argument handling, rendered output, live layouts, or recipes: read references/testing.md.

Open only the references required by the task.

Apply These Defaults

For one small command, use a plain Julia function plus Base @main on Julia 1.11+.
Use a Pkg app only on Julia 1.12+ when package installation is part of the requirement and the project accepts that Pkg app support is currently experimental.
Add a CLI framework only for meaningful parsing, help, completion, or subcommand needs. Keep Comonicon for compatible existing projects; do not make it the default.
Use plain text first, Term renderables second, and a Term live app only when keyboard interaction or continuously updated layout is required.
Use PrettyTables, via handle-julia-data, for ordinary tabular reports. Use Term.Tables.Table only inside a Term composition.
Target Makie 0.24's ComputeGraph for new reactive recipes. Do not copy pre-0.24 Observable mutation patterns into new code.
Test pure interface logic with explicit argument vectors and IOBuffers. Avoid elaborate mocks; add a small end-to-end smoke test only where the installed command contract matters.

For Cmd, environment, pipeline, process-I/O, deadlock, task, or thread details, use orchestrate-julia-workloads, especially its references/commands-and-processes.md file.