ieee-transactions
Format and submit papers to IEEE journals (Transactions, Journals, Letters, IEEE Access) and IEEE conferences using the IEEEtran LaTeX class or Word templates, covering journal vs conference modes, abstracts and index terms, numbered IEEE reference style, figures and equations, author biographies, page limits and overlength charges, IEEE PDF eXpress, copyright forms, double-blind options and ScholarOne/IEEE Author Portal submission. Use when writing for any IEEE venue, fixing IEEEtran layout issues, or checking IEEE submission compliance.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 1.6k
- Forks
- 483
01 前言 Front Matter
- name
- ieee-transactions
- license
- MIT
- metadata
- { "tags": "IEEE, IEEEtran, IEEE Transactions, IEEE Access, LaTeX, conference, journal formatting", "author": "Kalaris Labs (Sayan Chowdhury)", "version": "1.0", "category": "journal-formats", "maintainer": "Kalaris Labs" }
- description
- Format and submit papers to IEEE journals (Transactions, Journals, Letters, IEEE Access) and IEEE conferences using the IEEEtran LaTeX class or Word templates, covering journal vs conference modes, abstracts and index terms, numbered IEEE reference style, figures and equations, author biographies, page limits and overlength charges, IEEE PDF eXpress, copyright forms, double-blind options and ScholarOne/IEEE Author Portal submission. Use when writing for any IEEE venue, fixing IEEEtran layout issues, or checking IEEE submission compliance.
- compatibility
- TeX distribution with IEEEtran (CTAN), or Word with IEEE templates.
03 SKILL.md 正文
IEEE Journals and Conferences
Verify first (mandatory)
Each IEEE periodical and conference sets its own page limits, overlength charges, review model (single- vs double-blind) and submission system. Check:
- The journal's "Information for Authors" page (from its IEEE Xplore home) or the conference call for papers.
- IEEE Author Center: https://journals.ieeeauthorcenter.ieee.org/ (journals) and the conference author kit.
- The official template via the IEEE Template Selector (https://template-selector.ieee.org/).
Record: page limit (initial vs final), reference counting, overlength charges, anonymization rules, and whether a graphical abstract or multimedia is allowed.
LaTeX setup (IEEEtran)
\documentclass[journal]{IEEEtran} % Transactions/Journals
% \documentclass[conference]{IEEEtran} % conferences
% \documentclass[journal,compsoc]{IEEEtran} % Computer Society journals
\usepackage{cite} % compresses [1]-[4]
\usepackage{amsmath,amssymb}
\usepackage{graphicx}
\usepackage[hidelinks]{hyperref} % check venue rules; some conferences disallow bookmarks in final PDFs
- Don't change margins, fonts, spacing or column widths. Reviewers and IEEE production reject tweaked templates.
- Bibliography:
\bibliographystyle{IEEEtran}+\bibliography{refs}(IEEEtran.bst ships with the class). - Title and authors:
\title{},\author{}with\thanks{}for affiliations and funding (journal mode), and\IEEEauthorblockN/Ain conference mode. \begin{IEEEkeywords} ... \end{IEEEkeywords}for Index Terms after the abstract.- Figures:
figurefor one column,figure*for two. Tables use\captionabove the table. - Journal final versions include
\begin{IEEEbiography}author bios (with photos for many Transactions).
Content conventions
- Abstract: one paragraph, no citations/equations/abbreviations. IEEE Author Center recommends about 150-250 words (verify per journal). Include the key result.
- Index Terms: from the IEEE Taxonomy/thesaurus where possible, alphabetical.
- References: numbered in order of citation, in square brackets
[1], cited as nouns sparingly ("as shown in [3]"). Include DOIs where available. - Equations are numbered in parentheses and referenced as "(1)". Define every symbol.
- Units in SI. Use "Fig. 1" in text and captions per IEEE style.
- The first page footnote in journals includes received/revised dates (filled by IEEE) and funding.
Submission workflow
- Check page count and overlength charges. Supplementary material goes separately if allowed.
- Conferences: validate the final PDF with IEEE PDF eXpress (fonts embedded, Xplore-compatible) using the conference ID, then upload to the conference system.
- Journals: submit via ScholarOne Manuscripts or the IEEE Author Portal for that periodical. Complete the IEEE Copyright Form (eCF) or open-access license at acceptance.
- Double-blind venues: remove author info, anonymize self-citations ("[5]" in third person), and
strip PDF metadata (
\hypersetup{pdfauthor={}}). - IEEE Access and open-access journals charge APCs. Hybrid journals offer an OA option.
Common rejections at check-in
Modified template or margins; over page limit; missing index terms; non-embedded fonts; figures unreadable in grayscale (for print); references not in IEEE style; plagiarism/similarity score too high, including self-overlap with your own conference version (journals expect substantial extension).
Related skills
venue-templates, bibtex-hygiene, citation-verification, scientific-visualization,
arxiv-submission, rebuttal-and-response-to-reviewers.
04 同仓库更多 Skills
migrate-to-e2e
Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.
e2e
Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.
create-verification-skill
Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.
revid
Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.